This example introduce the user to simple provisioning configuration on CC32xx devices.
Board_LED0
- Blinking led Indicates disconnected. Led on indicates connection establishedBoard_LED1
- Led on indicates error occurredBoard_LED2
- Led on indicates error occurred and while blinking, indicates that the board is trying to connect to AP.Establish connection between CC32xx device to a specific AP using the Android \ IOS mobile application
Build the project and flash from the debugger or by using the SimpleLink Uniflash
Open a serial session (e.g. HyperTerminal
,puTTY
, etc.) to the appropriate COM port.
The COM port can be determined via Device Manager in Windows or via
ls /dev/tty*
in Linux.
The connection should have the following settings
Baud-rate: 115200
Data bits: 8
Stop bits: 1
Parity: None
Flow Control: None
The SimpleLink Wi-Fi provisioning process is divided into the Configuration stage and the Confirmation stage. The process begins with the configuration stage. During this stage, the SimpleLink Wi-Fi device waits for the end user to provide (using an external device such as a smartphone or tablet running a dedicated provisioning application) the information needed to connect to the wireless network as follows:
• Network name (SSID)
• Password
• Device name (optional)
• UUID (optional)
The device internally saves the provided network information into its serial flash memory as a new profile. Once a profile is successfully configured, the device moves to the confirmation stage. The confirmation stage tests the profile that was configured during the configuration stage. During the confirmation stage, the device tries to connect to the wireless network found in the new configured profile. If the connection is successful, the device also tries to provide feedback about the successful connection to the user’s smart phone provisioning application, which configured the profile. A connection is defined as successful if the WLAN connection is established, and an IP address is acquired. If the connection is successful, and the feedback is delivered to the user, the confirmation stage is successful, and the provisioning process successfully ends. If the connection attempt fails, or if it is successful but the feedback is not delivered to the user, the confirmation stage fails, and the device moves back to the configuration stage. At this point, the user’s smart phone provisioning app can ask the device to send the fail reason of the previous confirmation attempt, and configure a new profile.
Please install the latest CC32xx Service Pack in order to get the most optimization and lowest current consumption.