You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Will need to do a bisect to find the offending commit, but essentially somewhere between the crates.io release and current main there is a regression where i2c doesn't fail it just reads back 0xFF. This was produced on an F2 board, but it more than likely applies to other chips with i2cv1.
Blocking of course works fine.
The text was updated successfully, but these errors were encountered:
Will need to do a bisect to find the offending commit, but essentially somewhere between the crates.io release and current main there is a regression where i2c doesn't fail it just reads back 0xFF. This was produced on an F2 board, but it more than likely applies to other chips with i2cv1.
Blocking of course works fine.
The text was updated successfully, but these errors were encountered: