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
We need to decide how strictly we adhere to MicroPython I2C API.
Currently for reading from the I2C bus we should be following what MicroPython expects.
However for I2C.write we should be returning the number of ACKs received. Right now we enqueue all of the transfer data into one request and send that to the virtualiser, in order to follow the API though we would have to do a request for each byte of data and wait for a response and check if it is an ACK.
Less efficient than the current approach, but I guess I2C and MicroPython are not for efficiency. We should probably just follow the API in this case.
The text was updated successfully, but these errors were encountered:
We need to decide how strictly we adhere to MicroPython I2C API.
Currently for reading from the I2C bus we should be following what MicroPython expects.
However for I2C.write we should be returning the number of ACKs received. Right now we enqueue all of the transfer data into one request and send that to the virtualiser, in order to follow the API though we would have to do a request for each byte of data and wait for a response and check if it is an ACK.
Less efficient than the current approach, but I guess I2C and MicroPython are not for efficiency. We should probably just follow the API in this case.
The text was updated successfully, but these errors were encountered: