ESP32-c3 Build Fixes, add docs for flashing apps #3218
Merged
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.
Pull Request Overview
This PR fixes the following warning from esptool when running
make flash-app
:It seems that the flashed apps seem to overwrite critical regions of flash, causing the board to enter a infinite loop of trying to boot tock and failing. In order to recover from this I had to re-flash the tock kernel and apps.
Solution: add
--dont-append-digest
as the warning suggests, resolves issues with the boot loop.Additionally, I add some extra documentation detailing how to flash apps to the board. It should save others some time in the future.
To reproduce this issue:
make && make flash
make flash-app APP=../../../libtock-c/examples/<some-app>/build/rv32imac/rv32imac.0x403B0060.0x3FCC0000.tbf
This results in an infinite loop of trying to boot tock and failing:
Testing Strategy
Repeat the reproduction steps, it should not result in the bootloader failing to boot Tock.
TODO or Help Wanted
Someone else to validate this would be nice
Documentation Updated
Formatting
make prepush
.