-
Notifications
You must be signed in to change notification settings - Fork 7.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in vPortCPUInitializeMutex #1588
Comments
I believe this happens because the system is out of low memory when |
Just for information, this looks similar to already reported issue here, As mentioned above, fix for this is in progress, and should get integrated in IDF soon. |
Fixed with 16de6bf. |
espressif#1869 exposed a resource exhaustion issue. The current HAL layer for I2C support is designed to use a shared interrupt, But, during debugging to solve the interrupt overloading condition identified in espressif#1588, and the generation of pr espressif#1717, the interrupt allocation parameters were changed. This change was unnecessary, the code will work successfully with shared interrupts. So, there is no need to assign a private interrupt for each I2C peripheral.
I use spi ram extension.
I saw a crash in e676676:
The text was updated successfully, but these errors were encountered: