2 replies to this topic

[Paul Newton]

I am looking at using a netduino to test a slave I2C device that is being developed for us. We currently have a problem where the slave holds the clock line of the I2C bus low because it is busy, and subsequently the clock gets stuck low for an extended period of time. (The concept of holding the clock low is a standard one to allow the slave to process bytes already received.) Something has gone wrong, but it is not clear why. Hence I wanted to use a different master device with known working firmware to run some tests. My question is: Does the I2C implementation in the netduino support the remote slave device holding the clock while it is busy? I ask because the company developing the I2C slave device say their own test device does not support this. Thanks - Paul

[Mario Vernari]

Hello Paul. The I2C bus management is done directly by the Atmel MCU: I guess there's no much firmware involved in it. Thus, the "clock stretching" feature (as the Atmel calls it) should be fully supported. Hope it helps. Cheers

[Paul Newton]

Hello Paul.
The I2C bus management is done directly by the Atmel MCU: I guess there's no much firmware involved in it. Thus, the "clock stretching" feature (as the Atmel calls it) should be fully supported.
Hope it helps.
Cheers

I had hoped that would be the case.

Thanks Mario