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.

Compiler/CC3200-LAUNCHXL: Application bootloader OTA update

Part Number: CC3200-LAUNCHXL
Other Parts Discussed in Thread: CC3200

Tool/software: TI C/C++ Compiler

Hi,

    I am using the CC3200 in our project, is it possible to do Application bootloader OTA update on module?

Thanks,

Nagaraj

          

  • Hi,

       I have tried downloading the custom Application Bootloader bin file from server and writing to the "/sys/mcuimg.bin" filesystem and resetting the MCU, Module is not running with new updated application bootloader binary. Can you please guide on this OTA update?

    Thanks,

    Nagaraj GH

  • Hi Nagaraj,

    Yes, it is possible to update the CC3200 firmware over the air.

    Please follow the instructions in the CC3200_OTA_Update_Application_Note (within the SDK/docs).

    The Application Bootloader image just enables a secondary bootloader that select one of your functional images (/sys/mcuimg1.bin (factory reset image), /sys/mcuimg2.bin or /sys/mcuimg3.bin) that will be executed.

    Br,

    Kobi

  • Hi Kobi,

               Thanks for reply, I have gone through document which you have mentioned, It is documented on OTA of User Application and service pack OTA update, I could not find on Application bootloader OTA update. Is it we need to commit the application bootloader using FLC library or only we need to reset the MCU to deploy the new application bootloader on OTA update.

    Thanks,

    Nagaraj GH

  • Hi,

    Why would you like to update the application bootloader?

    I think you can update "/sys/mcuimg.bin" without any issue (the FLC will handle/modify "/sys/mcuimgA.bin" - which is reserved for the MCU image), but you shouldn't - the app-bootloaderit is part of the OTA solution, and is not part of your your application code.

    After any change to MCU files, you will need to reset the MCU.

    Br,

    Kobi

     

  • Hi kobi,

                   We added header and footer appended in binary file for secure OTA, we modify bootloader to parser the binary file and copy the MCU file to SRAM, Some of the modules are in customer field to secure the OTA on module, so we need to do application bootloader OTA which are in field. I am able to download the application bootloader to module from server successfully but application bootloader is  not getting boot up after MCU reset.

    Thanks,

    Nagaraj

  • Basically, you just need to write the "/sys/mcuimg.bin" (with or without the FLC driver).

    If the file is (re)written successfully (with your own app_bootloader content) - then it will be executed after the reset.

    Br,

    Kobi