Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adhering to MicroPython I2C API #20

Open
Ivan-Velickovic opened this issue Mar 7, 2024 · 0 comments
Open

Adhering to MicroPython I2C API #20

Ivan-Velickovic opened this issue Mar 7, 2024 · 0 comments

Comments

@Ivan-Velickovic
Copy link
Collaborator

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.

@Ivan-Velickovic Ivan-Velickovic added this to the 0.1.0 milestone Mar 15, 2024
@Ivan-Velickovic Ivan-Velickovic removed this from the 0.2.0 milestone Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant