2012-11-29 09:44 AM
I've been experimenting with the CPAL I2C library and as a test I'm sending a short string of bytes to an external device. I'm the only one on the I2C bus and I'm configured as an I2C master.
Does anybody know why the 'stop' of the I2C write command in the CPAL library is implemented as a time-out which is calling a user-callback function (where the stop is actually issued) and is not simply sent directly at the end of the communication? #stm32-cpal-i2c2012-11-30 12:02 AM
> Does anybody know why the 'stop' of the I2C write command in the CPAL library is implemented
> as a time-out which is calling a user-callback function (where the stop is actually issued) > and is not simply sent directly at the end of the communication? Can you please explain how did you come to this conclusion? JW2012-11-30 12:02 AM
[sorry, double post due to the crap used here instead of proper forum software - deleted]