Closed MrKevinWeiss closed 5 years ago
@smlng This was a pretty stupid bug in the i2c_2.c implementation for stm f1 or f4. It may be better to verify the error I get is a NACK?
I look forward to your feedback.
you seem to have an outdated master branch there are some conflicts
How do you want to do this, should we trigger manual tests first or just let it show up in the HiL nightlies (instamerge)?
How do you want to do this, should we trigger manual tests first or just let it show up in the HiL nightlies (instamerge)?
I will run them manually later today, if it looks good I'll merge and we see official result tomorrow.
Could you also run it against maybe a commit from last week so we can see the error?
tested (and works) with latest master on nucleo f4, but fails (as expected) on older commits (e.g. last release). ACK!
Super cool. And so it starts!
A bug was found when multiple nacks due to read bytes were issued. This test identifies this bug by reading the incorrect bytes multiple times then trying to recover with read byte.