Replace rtc_get_reset_reason(0) with esp_reset_reason() #86
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
theelims
approved these changes
Apr 10, 2025
JuergenLeber
pushed a commit
to JuergenLeber/ESP32-sveltekit
that referenced
this pull request
Nov 2, 2025
Replace rtc_get_reset_reason(0) with esp_reset_reason()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The current implementation using rtc_get_reset_reason(0) only retrieves the reset reason for CPU 0. This poses a problem since the user application typically runs on CPU 1, where programming errors such as panics or exceptions are more likely to occur.
I solved this by switching to the esp_reset_reason() function, which provides a more accurate reset reason for both CPUs at the same time.