This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220S-LAUNCHXL: OTA update when the device is in AP mode

Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH

Am I able to update the cc3220 if I only use it in AP mode?  http://www.ti.com/lit/an/swra510/swra510.pdf 

  • Hi Andrew,

    The OTA library which is in the focus of this document - requires that you have an internet connection (to connect to the cloud server). This requires station mode.
    Chapter 9 talks about Local Link support, which you may use instead.
    Please refer also to the "Local OTA" Example within the SDK.

    Br,
    Kobi
  • Thanks Kobi, it appears that the Local OTA example still requires the cc3220 to connect to an AP. Is it possible for the CC3220 to act as an AP and have a laptop, for example, upload the update file to it?
  • Hi Andrew,

    Yes, it should be possible (relatively easy fix).
    Once they are connected as station and AP and the Simplelink will activate the HTTP server (and maybe DNS server to make it easier for the mobile phone to get the IP address).
    The mobile phone should then connect to the HTTP server (like in the example).

    Br,
    Kobi
  • I'm already using the http server as the primary interface. So I suppose I just need to include the local OTA source pieces to my project and put provisions in my webpage to upload a file to trigger the update?  Although it appears that I must use the https for the OTA update?

  • It is recommended that you use HTTPS but it is your choice.
    You better look also on the html/js files that are provided with the local OTA example (check under the Uniflash/ folder within the example).
    You can replace them with your content but make sure you are aware of this part as well.

    Br,
    Kobi
  • OK, So it appears that it also sets up a secure socket, 5432, for the update progress.  I'm guessing I can just set that socket up to be unsecured in the otaReportServerTask(void *pvParameter) and forgo ConfigureHttpServer() so it leaves the primary http port as unsecured.  Does this sound correct to you?

    It also appears, I haven't tried yet, that if I can configure the device to AP mode instead of station and then bypass the StartConnection, it should kick off the appropriate events in the state machine to allow a local OTA update when the OTAPutCallback is called.

    Thanks

  • Hi,

    Yes, you can use both a secure socket for the OTA and non-secure one for your main task.

    The HTTP events should not be affected by the move to AP mode.

    Br,
    Kobi