On 11/12/22 08:57, Wolfram Sang wrote:
2. i2ctransfer -y 6 w9@0x65 0x00 0xff-
Always nice to see 'i2ctransfer' in action!
While at it do not test the return code from i2c_slave_event() for the
I2C_SLAVE_WRITE_RECEIVED since to my understanding this hardware cannot
generate NACK to incoming bytes
Not even on the last byte? That would be bad. If a backend encounters a
problem, there is no way then to communicate that back to the
controller.
Yeah, that's how I understood it. HW has an optional register (I didn't
check is it enabled on our HW) that enable generation of NACK for the
incoming data byte but it can be enabled only when the controller is
disabled and slave is inactive so it doesn't look very useful.
Jarkko
