Is your feature request related to a problem?
Currently, esp_ota_resume() allows interrupted OTA updates to continue without restarting the flashing process from the beginning. However, this capability is primarily applicable to full firmware image updates.
For devices using delta OTA updates, an unexpected power loss during the update process typically requires restarting the entire update from the beginning. This results in:
Additional network bandwidth consumption
Longer update times
Increased server load
Poorer user experience, especially on low-bandwidth or metered connections
Describe the solution you'd like.
Extend the OTA framework to support resumable delta OTA updates by:
Persisting delta update progress information in non-volatile storage.
Allowing interrupted delta patch downloads to resume from the last successfully processed offset.
Supporting continuation of patch application after device reboot or power restoration.
Providing APIs similar to esp_ota_resume() for delta OTA workflows.
Describe alternatives you've considered.
There is no alternative currently now, for this feature
Additional context.
No response
Is your feature request related to a problem?
Currently, esp_ota_resume() allows interrupted OTA updates to continue without restarting the flashing process from the beginning. However, this capability is primarily applicable to full firmware image updates.
For devices using delta OTA updates, an unexpected power loss during the update process typically requires restarting the entire update from the beginning. This results in:
Describe the solution you'd like.
Extend the OTA framework to support resumable delta OTA updates by:
Describe alternatives you've considered.
There is no alternative currently now, for this feature
Additional context.
No response