Parse error near *what you just said*. Wut?
I feel like we're playing microcontroller Mad Libs.
"I don't like this microcontroller because ________'s
(vendor) __________
(product line) has a terrible _________
(feature) implementation! For example it, always _________
(negative trait), AND, if you try and compile with ___________
(compiler or compiler option), the code will always ___________!
(phrase describing an undesirable state)Instead, I recommend everyone use __________
(competing product) which at the very least mentions its braindead ___________
(poorly-implemented peripheral or library) in the datasheet errata!"
I might consider buying someone an STM32 development board if they'll learn enough about its apparently well-known i2c flaws to fill in the blanks for the rest of us.
![Wink ;)](https://www.eevblog.com/forum/Smileys/default/wink.gif)
So far, all we know is it's really bad, has been bad for a while, and seems to be equally bad across the product portfolio. Does it spontaneously catch fire? Get stuck in infinite clock stretching? Only communicate with peripherals whose addresses are prime numbers? Nooooobodyyyyy knoooowwwwsss...