Variable-length I2C transmissions

RE: Variable-length I2C transmissions

Sigurd — Wed, 22 May 2024 15:44:58 GMT

Hi,

Yes, that might be the best solution. Another approach might be to use i2c_write_read_cb() with the max numbers of bytes possible to read, and then discard the excess bytes. But it sounds like creating a new special I2C read function is the best option.

RE: Variable-length I2C transmissions

mlac — Tue, 21 May 2024 20:12:10 GMT

Hi Sigurd,

I have to use a single I2C transaction for reading because the slave is implemented this way. Should I extend Zephyr with a special I2C read function that satisfies my requirements? Based on the API reference, I don't see any other solutions.

RE: Variable-length I2C transmissions

Sigurd — Tue, 21 May 2024 10:29:21 GMT

Hi!

Maybe you could try splitting the operation in 2.

First a i2c_write_read_cb(), and then a i2c_read() with the rest of the bytes ?

RE: Variable-length I2C transmissions

Amanda Hsieh — Fri, 17 May 2024 21:13:56 GMT

Hello,

Most of the staff is away for a long weekend in Norway, so there will be some delays in response time. I appreciate your patience.