OTA - esp_ota_mark_app_invalid_rollback_and_reboot()
Posted: Wed Mar 19, 2025 1:57 am
Can esp_ota_mark_app_invalid_rollback_and_reboot() be used AFTER esp_ota_mark_app_valid_cancel_rollback()?
Here is an example:
A new release is made and it is loaded via a OTA process. During the first run - it appears all is ok so esp_ota_mark_app_valid_cancel_rollback() is executed. BUT - let's assume the change impacted an SPI SD Card process and since the SD Card usage is NOT guaranteed to be executed the first run - a issue was not found until some time (multiple reboots) later. When the issue IS identified - can esp_ota_mark_app_invalid_rollback_and_reboot() then be called to make THIS image not usable and revert to the prior OTA image?
Thanks in advance for any insight.
Here is an example:
A new release is made and it is loaded via a OTA process. During the first run - it appears all is ok so esp_ota_mark_app_valid_cancel_rollback() is executed. BUT - let's assume the change impacted an SPI SD Card process and since the SD Card usage is NOT guaranteed to be executed the first run - a issue was not found until some time (multiple reboots) later. When the issue IS identified - can esp_ota_mark_app_invalid_rollback_and_reboot() then be called to make THIS image not usable and revert to the prior OTA image?
Thanks in advance for any insight.