You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm new to arduino (but with i2c driven wiritten on 6805 and 8051 25 years ago..), this issue could be completely wrong. I'm using the python read_i2c_block_data for master, a PI with I2c at 10 kHz and attiny45 at 8 MHz for the slave
If for some reason the onRequest callback doesn't provide any byte (with TinyWire.send) i2c slave feature is definitively lost . I studied the code but didn't found anything.
The workaround is to always send some data in the callback.
Thank for your library which is very helpfull.
Benoit
The text was updated successfully, but these errors were encountered:
Hello,
I'm new to arduino (but with i2c driven wiritten on 6805 and 8051 25 years ago..), this issue could be completely wrong. I'm using the python read_i2c_block_data for master, a PI with I2c at 10 kHz and attiny45 at 8 MHz for the slave
If for some reason the onRequest callback doesn't provide any byte (with TinyWire.send) i2c slave feature is definitively lost . I studied the code but didn't found anything.
The workaround is to always send some data in the callback.
Thank for your library which is very helpfull.
Benoit
The text was updated successfully, but these errors were encountered: