• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 62 subscribers
  • Views 170 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TPS65910: I2C glitch

Patrick Zeng
Intellectual 1090 points
Part Number: TPS65910

Hi team,

  I noticed the the doc mentioning the TPS65910 not handling well glitch on I2C. Solution is to repeat I2C access. How much time we should delay after 1st attempt and before the 2nd attempt? 

  Thanks.

Regards,

Patrick

  • 0
    TI__Mastermind 30260 points
    Patrick,

    The Errata document you are referring to states: "In the current design, the SCL line must toggle two times to detect a new start event and completely restart the I2C access."

    It does not appear to be a time-based issue. It is relatively common for the master in an I2C bus to toggle the CLK line up to 8 times if it detects that there is an issue with the bus, typically when the SDA line is held low (a "hung bus").

    If you are suspicious that a glitch has occurred and the data may be corrupted, you can repeat the same I2C transaction, or you can perform a "dummy" read to pulse the clock before sending additional data.