We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I encountered this bug in rp-rs/rp-hal#825, and a look at the I2C code in embassy-rp shows that it has the same bug.
In essence an SR is sent between operations of equal type, this can cause unexpected behavior in e.g:
fn write(&mut self, mut reg: u16, data: &[u8]) -> Result<(), Error<I2C::Error>> { self.i2c.transaction(self.address, &mut [Operation::Write(®.to_be_bytes()), Operation::Write(data)])?; }
as to avoid the SR all data must be copied into a single slice.
The text was updated successfully, but these errors were encountered:
It turns out the bug wasn't in the place I thought it was, and embassy-rp seems to handle it correctly, my bad.
embassy-rp
Sorry, something went wrong.
No branches or pull requests
I encountered this bug in rp-rs/rp-hal#825, and a look at the I2C code in embassy-rp shows that it has the same bug.
In essence an SR is sent between operations of equal type, this can cause unexpected behavior in e.g:
as to avoid the SR all data must be copied into a single slice.
The text was updated successfully, but these errors were encountered: