• State Not Answered
  • Locked Locked
  • Replies 6 replies
  • Subscribers 22 subscribers
  • Views 4679 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Shorting scl and sda lines in the board

Eilu Y

Hi,

I am working on tv board which has a i2c controller connected to a eeprom slave.
we are trying to check the i2c controller behavior,when SCL and SDA line are shorted using any metal device.

The behavior i observed is that i am getting a busy status even when both signal are high.Because of this unable to do another transaction.
But above thing can be recovered using soft reset.

The busy signal even arises during transactions with slave, so the software is not able to predict the controller behaviour during shorting.

Is there anyway we can determine the shorting of SCL and SDA line ?

Regards,
Eilu

Parents
  • 0 in reply to ²erik malund

    Well, any I2C test should introduce communication errors on the I2C data to verify that the firmware can reinitialize and get the connected devices to resynchronize again. It is, alas, quite common that "commercial" software fails something as simple as this.

    Having one unit, it may run for 10 years without any issues. Having 10k units out, a couple of them will for some reason do get an extra clock pulse or similar - the state error should automatically recover without a need for a full reset of the hardware.

Reply
  • 0 in reply to ²erik malund

    Well, any I2C test should introduce communication errors on the I2C data to verify that the firmware can reinitialize and get the connected devices to resynchronize again. It is, alas, quite common that "commercial" software fails something as simple as this.

    Having one unit, it may run for 10 years without any issues. Having 10k units out, a couple of them will for some reason do get an extra clock pulse or similar - the state error should automatically recover without a need for a full reset of the hardware.

Children
  • 0 in reply to ImPer Westermark

    Well, any I2C test should introduce communication errors on the I2C data to verify that the firmware can reinitialize and get the connected devices to resynchronize again.

    agreed and (s)he has that

    "[BUSY stays on] when SCL and SDA line are shorted .... But above thing can be recovered using soft reset."

    Erik