Use esp reboot counter to downlod a valid fw after 3 reboot #530
Conversation
This file contains 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
…U bootloader makes no sense
… a NINA W102 module
… maximum size which is available for the SNU second stage bootloader. In case of the MKR VIDOR 4000 the necessary FPGA bitstream is injected in the binary image above the usable flash of the MCU by the build system. When using the SNU for the MKR VIDOR 4000 we have to rely on the bitstream being already in place (not a unrealistic assumption, given that the SNU is compiled into a complete Vidor binary + fpga application).
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is based on the PR #512 and linked to the reboot counter in nina-fw (arduino/nina-fw#47).
In case we are trying to flash an invalid fw, a reboot is triggered. Whenever a reboot is done, the counter stored in the file "bootcounter.bin" is incremented. This patch introduces a check on the NiNaBoot side: after 3 consecutive reboots, a valid fw is downloaded from a suggested URL.
The WiFi credentials in Usage.ino need to be set to working ones, as well as the URL in NiNaBoot.ino from which the binary of the new fw must be downloaded.
Once a valid fw is downloaded and the continuous rebooting is stopped, the file containing the reboot counter is erased.