On 15/06/2010 22:51, Bertrik Sikken wrote:
But, as far as I understand, this delay applies to an i2c driver and generally i2c devices should be fairly tolerant to clock variations. The fact that the correct functioning seems so sensitive to i2c delays suggests to me that maybe something else is wrong. For example, could there be a problem in the bit-banged i2c implementation itself?
You're almost certainly correct, and this should be investigated. My main concern was simply making the device work as well as it did before the compiler change, and the obvious way to do that (to me) was to fix the delay loop. If there is a greater problem, then of course that should be investigated.
Another area to look into would be the Telechips SoC's built-in I2C controller, as there should be no need for bit-banging at all... Rob
