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.

CCS/CC3220SF-LAUNCHXL: OTA frozen when trying to do Local_OTA on CC3220

Part Number: CC3220SF-LAUNCHXL
Other Parts Discussed in Thread: UNIFLASH, CC3220SF

Tool/software: Code Composer Studio

I am trying to get the local OTA example to work.  I have the uniflash tool for desktop installed, and am using CCS v10.  

After creating a hotspot on my mobile device, I was able to connect the CC3220 to it, and saw that it was waiting for an "

[Local ota task] waiting for new ota upload..."

(I had modified the source code correctly to connect to my hotspot and provide the WIFI key).

I connected my PC to the same hotspot, and went to the dev.ti.com ota.html link.  I then went to my workspace (local_ota/example_tar), and tried to upload the cc3220sf_local_ota_freertos_ota.tar file.  The website got stuck and nothing happened.  

What am I doing wrong?

  • Did you get any more terminal logs?

    Can you get sniffer log to check the status of the HTTP connection?

    Is the SimpleLinkNetAppRequestEventHandler() being called? Does the PUT request is being called?

    Can you suspend the execution using the debugger and check that the program still runs as expected?

    I'm not sure what do you mean by "dev.ti.com ota.html link", do you see the ota web page on the browser? do you see the device version information? (this means that the HTTP GET request is working).

    You can also capture the NWP log (see instruction in chapter 20.1 of the programmer's guide: https://www.ti.com/lit/ug/swru455l/swru455l.pdf) which may provide more info on the issue.

    Br,

    Kobi

  • Kobi,

    Thank you for the quick reply!  I realize I didn't provide enough background information, so I will first show what has been programmed to the CC3220 using uniflash.

    The MCU img is the .bin file from the project that was built.  On my PC it is here: \local_ota_CC3220SF_LAUNCHXL_freertos_ccs\MCU+Image

    The Service Pack File is from the SimpleLink SDK.  On my PC it is here: C:\ti\simplelink_cc32xx_sdk_4_20_00_07\tools\cc32xx_tools\servicepack-cc3x20

    The user files that I burned into the CC3220 device look like this:

    Am I missing any essential files?  I previous posts I saw that others had included .zip files.  However, I do not know how to include these, if they are needed.  

    My serial terminal log looks like this:  

    Regarding the SimpleLink Handler call, no, this event handler is not being called.  However, the CC3220 does connect to nmdev and is waiting for OTA:

    Regarding the ota.html, I am referencing this website.  Please, keep in mind that both the CC3220 and my PC are connect to my mobile hotspot "nmdev":

    I have suspended the debugger, and the program does allow the CC3220 to connect, as stated.  However, I cannot load an image via the ota.html.  I go to the directory (C:\ti\simplelink_cc32xx_sdk_4_20_00_07\examples\rtos\CC3220SF_LAUNCHXL\demos\local_ota\example_tar), and attempt to load the freertos file: 

    Now, as you can see these files are in the SDK and not in my project's workspace.  Should they be moved to the workspace?  

    I can get more HTTP logs, but wanted to get you this information first.  I'm probably wrong in the setup.

    Thank you,

    Noah

  • As a follow up, I used WireShark to sniff some of he HTTP packets.  Here are the results, filtering on IP address 192.168.43.105. 

    Interestingly, when I tried to upload the .tar file using ota.html, I did not see any more activity on this IP address - it remained frozen.

    WireShark_simplelink_export.xlsx

  • Hi Noah,

    The ota.html (with all the other user files) should be programmed to the device (using uniflash).

    Then once your PC is connected to the simplelink device.

    open a browser and access the ota.html on the device (i.e. using "mysimplelink.net/ota.html" or "<device-ip-address>/ota.html").

    See the readme of the local OTA for more details.