add I2C_RX_FIFO_OVF_INT_ST handling to i2c_isr_handler_default #4342
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
Fixes crash on ESP32 when I2C FiFo overflows and interrupt function is unable to handle crash and throws this error: [E][esp32-hal-i2c.c:1013] i2c_isr_handler_default(): unknown int=4
Contributor
Author
|
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.
I have run into a Problem where my ESP32 would crash with this error message:
[E][esp32-hal-i2c.c:1013] i2c_isr_handler_default(): unknown int=4It turns out
i2c_isr_handler_default()does not handleI2C_RXFIFO_OVF_INT_STat all which ultimately leads to a crash. Handling it the same way as a I2C_RXFIFO_FULL_INT_ST fixes the crashing and only leads to gracefully handled errors in the I2C transaction.