-
Notifications
You must be signed in to change notification settings - Fork 19
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
[bug] failure to perform I2C scan of device(s) connected over custom pins #84
Comments
Hi @lyusupov, To workaround this issue, try to add a dummy write:
The output should be:
We'll address this issue in the next core release. |
I've rebuilt and re-flashed the I2C scan sketch above with recent Core 2.2.0
The issue still remains:
|
FYI I've raised this issue with Arduino Support. |
Hey! It's not an issue, we decided to force "success" if no data is sent. To check if an address is valid or not, add a dummy write:
|
@leonardocavagnis I've tried the approach you've stated and as it is actually sending a byte it has some unintended consequences. For example, it seems to force a AHT20 into an inconsistent state, requiring soft restart. Therefore, it really needs a fix. |
@dansiviter Understood! According to the Seed_Arduino_AHT20 library, you can send a "start command" to the sensor and waiting for a reply within a time span. |
Hardware
BGM220
Core version
2.1.0
Arduino IDE version
any
Operating system
any
Radio stack variant
No radio
OpenThread Border Router device (if using Matter)
none
Issue description
I use an I2C module with 2 devices connected to SDA=D1 (PC0) and SCL=D3 (PC2)
This is the scanner sketch:
When the sketch uses this Core built-in Wire library https://github.com/SiliconLabs/arduino/tree/main/libraries/Wire - it FAILs:
If I use the FlexWire library (software I2C) https://github.com/felias-fogg/FlexWire as a substitute for the built-in Wire library - the sketch works nicely
Serial output
No response
RTT output (if using Matter)
No response
Minimal reproducer code
No response
The text was updated successfully, but these errors were encountered: