x
Smartphone App
Networking Subsystem
Host
APIs blocked
Connect to AP
–ƒ”– •ƒ”– ‘•ˆ‹‰
?
‡ƒ”…Š ˆ‘” †‡˜‹…‡
ï
•
ƒ††”‡••
‡˜‹…‡
ï
•
ƒ††”‡•• ˆ‘—•†
Wait for profile configuration
Start profile confirmation
Provisioning ended
Provisioning Command
(Start APSC mode)
Profile added event
SmartConfig synced event
WLAN connected event
IP acquired event
Get confirmation result (HTTP)
Confirmation result Success (HTTP)
Confirmation status success event
Provisioning stopped event
APIs allowed
Usage Examples
216
SWRU455A – February 2017 – Revised March 2017
Copyright © 2017, Texas Instruments Incorporated
Provisioning
15.11 Usage Examples
15.11.1 Successful SmartConfig Provisioning
In
, a profile is configured using SmartConfig. The provisioned device connects to the wireless
network from the configured profile and waits for the smartphone app to contact its HTTP web server.
When the confirmation result is delivered to the smartphone app, the device sends the successful result to
the host, and stops the process.
Figure 15-3. Successful SmartConfig Provisioning
The APIs between the host driver and the networking subsystem (commands and events) are blocked
during the entire provisioning process. The host is allowed to send commands only after the
provisioning_stopped event arrives.