Add custom panic handler #16
Merged
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
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.
(ESP32 side not done yet so I still have to test if it works properly)
The idea here is that if a call to panic() is made the RP2040 will reboot and set a register accessible over I2C that indicates it has crashed.
SDK behaviour of panic() is to print ***** PANIC ***** with a reason to the UART then halt, that's not very usefull on the badge.
When the RP2040 crashes and reboots it resets the ESP32 too, so checking the register on startup and showing a message to the user indicating the reason for rebooting would help identify RP2040 problems on production firmware.
When compiled in debug mode the panic handler isn't modified so that crashes can be investigated with a JTAG debugger.