We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
doc.nit.ac.ir/.../3-Mazidi-8051.pdf
It was not me who said that, but I have done it. Unfortunately, some I²C hardware implementations are not as good as they should be.
Isn't that the truth, there seem to be plenty of cases where the IC designer clearly has little grasp about the implementation of the bus in a practical sense.
SPI and CRC implementation are also prone to lackluster design.
The key is to recognize when the hardware implementation is flawed or inflexible, and when a software solution could be appropriate. Keep an open mind.
Unfortunately, some I²C hardware implementations are not as good as they should be. So doing it the hard way is sometimes the only sensible way out of a tricky situation. Everybody can state anything, but it would be valuable o know which.
I have two cases from fora and one from experience where "I²C hardware implementations are not as good as they should be" was not true, it was "the implementer of code for the I²C hardware implementations that was not as good as he should be"