SWRU455M February 2017 – October 2020 CC3120 , CC3120MOD , CC3130 , CC3135 , CC3135MOD , CC3220MOD , CC3220MODA , CC3220R , CC3220S , CC3220SF , CC3230S , CC3230SF , CC3235MODAS , CC3235MODASF , CC3235MODS , CC3235MODSF , CC3235S , CC3235SF
When the provisioning process is started in APSC + external configuration mode, the device is ready to serve stations trying to connect to it (for AP provisioning), ready to handle SmartConfig transmissions (SC provisioning), and can allow the host to execute an additional external provisioning method that is not implemented inside the networking subsystem (for example: WAC).
In this mode, the host is allowed to send commands and receive events from the networking subsystem while provisioning is running. After the networking subsystem has successfully started the provisioning process, it sends the EXTERNAL_CONFIGURATION_READY event to the host, which indicates that the host may start executing its external provisioning method (for example: start listening on socket). At this point, the end-user may choose which method to use: AP provisioning, SC provisioning, or the external method implemented by the host application.
If the host application identifies that the end-user chose to use the external configuration method, it should stop the internal running provisioning process by issuing a PROVISIONING_STOP command (the host should also order the networking subsystem to stay in its current role after stopping the provisioning), and continue carrying out the external provisioning process.
If the end-user has configured a profile using one of the internal provisioning methods (AP or SC provisioning), the device must be restarted before it can continue the internal provisioning process. The networking subsystem sends a RESET_REQUEST event to the host, and the host should stop its external provisioning process (close all opened sockets, and so forth), restart the SimpleLink Wi-Fi device (by issuing sl_stop and sl_start commands), and wait for the internal provisioning process to end.