CC3235S: Rollback on sys/mcuimg.bin updates

Tomas Malmelöv

Part Number: CC3235S

Tool/software:

I have an OTA implementation where /sys/mcuimg.bin is sucessfully updated during an OTA, however, seems like it's "commited" as soon as the file is closed, not sure if that's how it should work.

Is it possible to postpone the commit of the image to after a reboot of the MCU i order to test to start the new image?

Tomas

1 month ago

0 Jan D 1 month ago

Guru 79905 points

Hi Tomas,

OTA updates are designed exactly by that way. After updating image you need to restart. When you detect pending for commit you can test functionality of your new image. After that you need to commit new image. If you not do that, you image will be reverted into previous state after reset (e.g. by watchdog reset).

Jan

0 Tomas Malmelöv 1 month ago in reply to Jan D

Prodigy 165 points

Ok, is that funciobality only part of the OTA lib in SDK? Or should it work the same no matter how I update the mcuimg.bin?

Tomas

0 Brandon Liu 1 month ago in reply to Tomas Malmelöv

TI__Prodigy 730 points

Hi Tomas,

The OTA functionality described does in fact apply to Simplelink devices, but I don't exactly understand your question. What functionality are you comparing when you talk about updating the mcuimg.bin?

Meanwhile, to learn more about OTA updates, you can find additional information in this manual.

Best,
Brandon Liu

0 Jan D 1 month ago in reply to Tomas Malmelöv

Guru 79905 points

Hi Tomas,

Technically this is part of sl_ filesystem. Please see SWRU455 chapter 8.9.

Jan

Wi-Fi

Wi-Fi forum

CC3235S: Rollback on sys/mcuimg.bin updates