-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
ESP32-C3 I2C read failure results in crash (IDFGH-5558) #7281
Comments
As stated above, I tried many combinations and have been able to isolate the issue to I2c. |
Hello @eyewy , |
@eyewy Any update? |
@eyewy BTW, it's hard to find the exactly commit of the "latest SP-IDF master" on 17 Jul 2021, |
I am also facing similar issue. I2C is not working with ESP32C3. I had tried with the i2c_tools example to scan i2c devices but it ended with the below message Version: IDF 4.4 |
Thanks for reporting and sorry for slow turnaround, fix is available 0b00831, we are also back porting to release branches. Feel free to reopen. |
On ESP32-C3, if for whatever reason I2C read fails, program crashes with following error code:
E (11861) task_wdt: Task watchdog got triggered. The following tasks did not res
et the watchdog in time:
E (11861) task_wdt: - IDLE (CPU 0)
E (11861) task_wdt: Tasks currently running:
E (11861) task_wdt: CPU 0: my_i2c_service
where my_i2c_service is a function that writes and reads to I2C interface of a sensor. It has a 1000ms delay inside the while(1) loop. It is used as follows:
xTaskCreate(my_i2c_service, "my_i2c_service", ECHO_TASK_STACK_SIZE, NULL, 5, NULL);
I am using latest ESP-IDF mater branch. 5.1k external pullup resistors. reading from BME680 sensor. The error/crash happens at a random time, and if I2C read fails, otherwise everything is ok.
Also, I used the nimble blehr example, where I modified the "blehr_tx_hrate" function to read the I2C sensor data and the transmit via BLE in this function. As this is a timed function (runs every 1000ms), I have not added any additional delay. Not sure why WDT is raised at some random time.
The text was updated successfully, but these errors were encountered: