Core 1 panic'ed (Interrupt wdt timeout on CPU1) on ESP32 #218
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.
Sometimes I got a core 1 panic (Interrupt wdt timeout on CPU1). The timeout occured in the expectPulse function. This was the case because the cpu stayed the most time (up to 1ms) in the while loop of this function when the sensor didn't deliver useable information. Because there is no timeout check in the critical section of the read-function, the expectPulse function was called 80 times, what lead under certain conditions to a wdt timeout - even with a default wdt timeout setting of 300ms.
I've just moved the timeout-check in the critical section and the problem disappeared.