OTA Strategy / disableReset vs disableUpdates

I’m trying to develop a strategy for OTA updates and I’m trying to determine when to use disable/enableUpdates vs disable/enableReset.

My firmware allows a user to run an operation that takes about 1 hour to complete. During this time it is not acceptable for my firmware to reset. It would be ok for the firmware to download an update in the background and only reset after the 1 hour task.

Is an acceptable strategy to disableReset, allow updates to happen naturally during the critical task, and enable the reset once the task is done? This would allow for a pending update to download during the critical task but not to reset until after it is done.

Or is it better to make use of disableUpdates and only enable and check for updates when the task isn’t happening at all and make sure I disableUpdates during the task.

Let me ping someone that might be able to help, @rickkas7 or @ParticleD are you able to assist?

My recommendation is to allow download but disable reset. That should work well.


1 Like

Let us know if Rick’s suggestion works!

Seems to be working! Thanks :slight_smile:

1 Like