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.

CC3220SF-LAUNCHXL: CC3220SF-LAUNCHXL

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

Hi All,

          I am using CC3220SF in my project. The CC3220SF is externally connected to another microcontroller "A"  via UART. I wanted to do an OTA upgrade of microcontroller "A" via CC3220SF module. The steps would be as follows:-

1) CC3220SF will be configured as a station and it will get internt connectivity.

2) The OTA file package (zip folder) should be received by CC3220SF from the server. It should detect if zip folder is for the microntroller A or for itself.

3) If OTA package file is for microntroller A, then CC3220SF module should transfer this zip folder to the microntroller A via UART. 

Is this possible to do in CC3220SF module?? Are there any examples available that I can check and implement?

Thanks & Regards,

Snehal

  • Hi Snehal,

    Yes, it is possible if firmware for another microcontroller fit into sFlash (SPI flash). You should not use ZIP file format for another MCU firmware if unpacking of ZIP file will be needed at CC3220. In this case you should stay with standard TAR package as is used by OTA code.

    There is not available example for exact same use case. But there is similar example for MSP432 with CC3120 here.

    Jan

  • HI Jan,

    Ok if I use TAR file. The tar file of microcontroller A will include its firmware file, key and manifest.json. Do I also need to include any other file in the package so that CC3220SF will accept it?? 

    Sorry if my questions sound naive. I am working on OTA for the first time.

    Snehal.

  • Hi Snehal,

    TAR is used to packing all files for OTA data transport. Commonly is OTA used for update of MCU image file for CC3220 and other files. Via OTA process you can update any files you want. That mean nothing prevent you add into OTA archive files for your other MCU. After your OTA ends, you will have in sFlash files with firmware for your another MCU. You will read this files from sFlash and sent them via UART into your another MCU.

    Jan