i have 2 devices need operate on i2c.
primary 1 requires bus run @ 400kbps baudrate because of volume of data needs read faster volume of data generated.
secondary device can run 400kbps, if master (the rpi) supports clock stretching, iirc doesn't. correct? believe it's hardware related, , cannot enhanced / fixed. correct?
believe joan's pigpio support i2c clock stretching via bit banging. correct?
tia
primary 1 requires bus run @ 400kbps baudrate because of volume of data needs read faster volume of data generated.
secondary device can run 400kbps, if master (the rpi) supports clock stretching, iirc doesn't. correct? believe it's hardware related, , cannot enhanced / fixed. correct?
believe joan's pigpio support i2c clock stretching via bit banging. correct?
tia
the current linux driver not support clock stretching although understand patch in pipeline.
pigpio support bit banged clock stretching couldn't usefully drive @ anywhere near 400 kbps (it use cpu). relevant python calls 3 bb_i2c_* functions.
pigpio support bit banged clock stretching couldn't usefully drive @ anywhere near 400 kbps (it use cpu). relevant python calls 3 bb_i2c_* functions.
raspberrypi
Comments
Post a Comment