-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Adding I2C Burst Reading/Writing feature #1495
Conversation
Any idea how we would test this? Do you have some code that works with MAX3010X that could be put int pico-examples? |
a bit confused at a very qucik glance; can't you just set |
@kilograham In the original implementation with "nostop" set to true, the start condition can repeat without sending a stop, allowing for repeated starts within a transfer. However, in burst mode, there is only one start and one stop condition, with several commands or data transfers happening continuously in between without any repeated starts or stops. |
@kilograham Is there a reason this didn't make it into the release? |
because it had merge conflicts |
Rename the functions. Lose the "mode" and "blocking" needs to be at the end. Just set restart_on_next in the caller rather than adding a parameter.
Actually, it was my mistake. |
Example here raspberrypi/pico-examples#512 |
@kilograham Apologies - could you review this again? |
I realize that the C-SDK of Raspberry Pi Pico does not support the burst mode operation in I2C (only supports normal and repeated start in reading/writing). As burst mode is an important I2C feature that is sometimes required in communication with several I2C slaves. e.g. MAX3010X. Hopefully, we can consider adding this feature to the current SDK.
Thank you