Closed TeXniKK closed 2 years ago
Hi @TeXniKK ,
Thanks for reporting this, I am going to try reproducing it and check what the issue is.
Hello guys
I am unable to reproduce this issue. I've tried on two ESP32S2 boards (esp32-s2-saola and esp32-s2-kaluga) with three I2C slave devices (DHT12, BMM150 and BMP280) attached. Same GPIOs (4/5). I ran i2cdetect
about 50 times on each board - no crash.
Fresh esp-idf clone: v4.4-dev-3540-g4e03a9c34c
@TeXniKK: does it crash for you as well when no I2C slaves are attached?
Thanks Felix
Hello @felmue ,
Thanks for your feedback, I tried on my side on an ESP32-S2-WROVER and commit b86fe0c66
and I was also unable to reproduce the issue.
I tried about 40 times with a gyro sensor tied on the bus and 50 times without any device but with a logic analyzer to detect whether the generated signals were correct or not. It turned out they were correct.
Hello guys. Thank you for verification. I'll check which exact I2C device allows to reproduce the issue and post details soon.
@TeXniKK Thanks for reporting, would you please help share if any updates for the issue? Thanks.
Closing this issue for now, feel free to re-open if you still encounter this problem
Environment
Problem Description
i2c_tool example crashes on ESP32S2 after running 'i2cdetect' command multiple times
Expected Behavior
i2cdetect command executed without errors and crashes
Actual Behavior
ESP32S2 crashes with
Guru Meditation Error: Core 0 panic'ed (Interrupt wdt timeout on CPU0).
Steps to reproduce
i2cconfig --sda=4 --scl=5
in ESP shelli2cdetect
multiple times (usually 5-10)// If possible, attach a picture of your setup/wiring here. SDA connected to pin 4, SCL connected to pin 5. Chips on I2C bus: 24LC32AT-I/OT, SHT20, PCF8533-based LCD
Code to reproduce this issue
Just use unmodified i2c_tools example from IDF
Debug Logs
Other items if possible