I2C_slave / i2c_legacy
Posted: Sat Jul 20, 2024 6:05 am
I2C_Legacy seems to have feature where you can have more granular control over the I2C communication.
i.e. you can receive x bytes, send a response and then acknowledge the response.
with i2c_slave it seems you can only read a predefined buffer size then transmit.
Also master for write will do i2c address << 1 and for read (i2c address << 1) | 1
with i2c_slave is there a way to know if its a read or write operation.
Im asking these questions because i see i2c legacy could be deleted any time, however i2c_slave does seem to have limited functionality unless im wrong?
i.e. you can receive x bytes, send a response and then acknowledge the response.
with i2c_slave it seems you can only read a predefined buffer size then transmit.
Also master for write will do i2c address << 1 and for read (i2c address << 1) | 1
with i2c_slave is there a way to know if its a read or write operation.
Im asking these questions because i see i2c legacy could be deleted any time, however i2c_slave does seem to have limited functionality unless im wrong?