-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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- S2 - i2c scan returns multiple bogus addresses #9931
Comments
The problem also appears in the feather TFT ESP32-S2
|
Adafruit Feather ESP32-S2 Rev TFT i2c scan tests with recent releases of CircuitPython.
Based on the CP 9.1.0 release notes the ESP-IDF was updated to v5.2.2. |
I think I have a fix for this via #9942. If you want to test an artifact: https://github.com/adafruit/circuitpython/actions/runs/12679605089 |
Thx dan. Looks like you got it. I tried with your current artifact on a ESP32-S2 REV TFT. Looks good picking up the local I2C battery monitor and a MCP23008 board I plugged in.
|
I tried the patched build on my stacked set of Feather boards, it worked fine. |
CircuitPython version
Code/REPL
Behavior
Testing just the ESP32-S2 Reverse TFT Feather (no additional Feather boards connected, nothing on the Stemma_QT port), the I2C scan returns many incorrect I2C addresses.
In this configuration, the only I2C address that should appear is for the built-in MAX17048 battery gauge on [0x36].
Description
Does not matter whether the i2c_scan uses board.I2C() or board.STEMMA_I2C().
Does not matter whether a LiPo battery is connected to the Feather.
Does not matter whether any other Feather modules are stacked with the ESP32-S2 Feather.
All of these variants result in the same issue: bogus addresses being detected.
Additional information
See this Forum thread for complete details (including investigation by "mikeysklar").
https://forums.adafruit.com/viewtopic.php?t=215740
The Forum thread has a lot of pictures showing a stack of Feathers attached to the ESP32-S2, but that doesn't matter. The issue happens even with no additional boards installed.
The investigation by mikeysklar shows that the issue happens on the ESP32-S2 Reverse TFT, but not on the ESP32-S3 Reverse TFT.
The text was updated successfully, but these errors were encountered: