Replies: 2 comments
-
I'm also experiencing this (there's an issue open since 2 days: #2026).
Since this is discussion, would you like to create an Issue with the above text, or join the existing one? :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please try again on main. For future reference, bug reports should be opened as issues as I completely missed this till now. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm trying to use
I2C
with aPN532
board.On ESP32 I managed to get it to work, however not without issues:
I2C
w/o timeout, I always received timeout errors, which doesn't sound right, I'd expect it to hang if there was a timeout, no? Maybe w/o timeout it defaults to timeout of 0?On ESP32S3
hal
code on the non-ESP32 does such conversion (unlike the ESP32 code).Looking at the
i2c.rs
code I found the code below, where it says that it requires a fix.But the code looks like it's written. So is timeout on non ESP32 (in my case ESP32S3) working or not?
Also, in the ESP32 the time_out_value is not converted to u8 before feeding into the register (and it's a
u32
), is that correct behavior?BTW, if it matters on the ESP32 I use
I2C0
and on ESP32S3 I useI2C1
.Beta Was this translation helpful? Give feedback.
All reactions