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.
Tool/software: Code Composer Studio
hai,
Wireless OTA Firmware update using Energia
i will try to same Lib but not working ,
any other option at OTA Firmware and program update with out TI APP ,using TCP/IP or Cloud Based Firmware Update
any other Example OTA at Energia
Thanks and Regards
SELVA
Hi Selva,
As per this thread (), please post any Energia questions to their main forum ( http://forum.43oh.com/forum/125-energia-tivaccc3xxx/ )
Otherwise, questions about technical details of the CC32XX/CC31XX devices can be asked on this thread, or feel free to open another thread if this one is locked.
Best regards,
Kristen
Hi Jan,
I recently learned something interesting about the CC3220 bootloader that would help for this energia issue and for any use case where you have a CC3220S binary but want to flash it onto a CC3220SF.
It turns out that the CC3220 bootloader checks the filename of the MCU binary to decide where to load code. If the mcu binary is named "/sys/mcuimg.bin", then it loads to RAM. If the mcu binary is "/sys/mcuflashimg.bin", then it will load to internal flash. If you think of the differences between a CC3220S Uniflash project and a CC3220SF uniflash project, one of the primary differences is that the "Select MCU Image" interaction provides a different filename to the filesystem. However, there is nothing stopping you from overriding this behavior of Uniflash by manually specifying the MCU image filename.
Thus, if you have a CC3220S binary and want the bootloader on the CC3220SF to treat it as code to load to RAM, you simply have to manually add the MCU image as file under /sys/ in Uniflash as "mcuimg.bin". You cannot use the Simple view to add an MCU image, nor use the "Select MCU Image" function, as those will automatically provide the device-appropriate MCU filename. You'll also need to manually set the proper filesystem flags that a MCU img should have, which are the failsafe,secure, and public write flags, but otherwise there are no real barriers to doing this workaround. Once you have provided a Energia binary as "mcuimg.bin", it can boot and run as expected from the external flash.
Your contribution with the bootloader is greatly appreciated, as shown by the help you've given in this thread, but I wanted to point out to future Energia + CC3220SF users that the above workaround is much simpler than using a secondary bootloader.
Regards,
Michael
Hi Michael,
Thank you for a update. Unfortunately support for CC3220SF (CC3235SF) is not great in Energia. Many things (libraries) should to be updated. Also absence of uploading XIP flash by JTAG/SWD may to be frustrating for someone. I think TI should invest some manpower to maintenance of this project. Because it slowly dying.
Jan