Tool/software:
Hi TI support,
I am using SimpleLink CC32xx SDK v7.10.00.13 and the out-of-box Local OTA demo for firmware update.
After the OTA update is downloaded and the device reboots, the SDK requires a commit within a limited time window, otherwise the update rolls back to the previous firmware.
I would like to know:
-
What is the default time window for committing an OTA update after a reboot?
-
Is there an official way to increase or configure this commit timeout in the SDK?
-
Are there any recommended practices to safely verify the new firmware before committing?
My use case:
-
Using local OTA (HTTP PUT /ota/update)
-
Verifying device functionality via GET /ota/verify before committing
-
I want to extend the verification time if needed, without triggering automatic rollback.
Thank you for your guidance.