ESP32 Dual Booting #157
Merged
ESP32 Dual Booting #157
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
20 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have two app partitions... why not use them?
This allows switching between the OTA partitions on the fly. If you flash via the web interface, this can be used to roll-back to your previous firmware... or to just switch between two firmwares on the same ESP32 for A/B testing without reflashing.
If you only flash a board over serial, app0 is always flashed - but if you use OTA, then app1 is flashed and the board is adjusted to boot from it instead. The next time you OTA update, app0 will be overwritten and you'll boot from it, etc.
This allows pressing "^" on the serial console to switch boot partitions between app0 and app1, if they both exist and appear to be valid. Could also be moved into the GUI, etc.