I have an OTA update routine which runs in line with what is being done in the example provided by TI. However in my OTA application I'm attempting to use the WLAN profiles to automatically allow the application to connect by simply issuing an sl_Start(0,0,0) or sl_Start(NULL, NULL, NULL) command. Problem is when the base application has setup the connection using WPS after rebooting into my OTA app the CC3200 refuses to connect. In fact it won't even obtain an IP address from the AP.
So I've tried adding the sl_WlanProfileGet to obtain the profile #0 information and then simply passing that on to a sl_WlanConnect. When I do this I get a return -89 (incorrect password) error. When this step is added an IP is acquired but there is still no connection to the AP.
Since the base application is able to reconnect with a simple sl_Start (even after re-booting out of the OTA app) I'm clueless why the OTA app can't do the same thing. Do I need to store AP credentials somewhere and pass them to the OTA app? Or am I missing a step in re-establishing the connection from the OTA app? Once the base app has established connection credentials I don't want to have to re-establish them for the OTA app if at all possible.
As a side note my AP is using WPA2. My CC3200 is the older 'HZ' version. The sl_Start returns a 0 (ROLE_STA) which is normal.