I2C Clock Stretching
-
Anything happening on the stretching part?
I have to get an Adafruit BNO055 up and running on LoPy before the end of March.
It is supposed to be used on a FiPy combined with a GPS for an Inertial Navigation System prototype project.
-
@iannucci I'm curious if you ever got this working. The TI documentation is a hot mess. If you did, can you post up some example code, please? =)
-
@daniel I'm happy to test, too. I'm seeing I2C problems any time a slave attempts clock-stretching.
-
@daniel I would be happy to test.
-
@livius and @iannucci I have good news, the hardware implementation of the I2C is ready and will be merged very soon.
-
-
I just implemented functionality for the TI BQ27441 Battery Fuel (Gas) Gauge today and was having no success in getting the device to respond until I hooked up an I2C debugger and saw that, when the battery gauge stretched the clock and then let go, the LoPy I2C interface never came back to life. So I've re-discovered this old problem. The short-term fix for this particular part is to slow its I2C transactions down to 10kHz (wasting energy in the process...).
Running MicroPython v1.8.6-464.
What is the status of the real clock-stretching fix?
Thanks.
