• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 48 subscribers
  • Views 807 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

INA226-Q1: I2C communication issue

Daniel Wang (auto)
Expert 5420 points

Part Number: INA226-Q1
Other Parts Discussed in Thread: INA226

Tool/software:

Hello team,

Is there any situation will cause abnormal I2C communication between the host and INA226: no response to the host (either ACK or NAK) for a long time, and the I2C bus is occupied and not released.

For example, chip overheating, voltage instability, frequent writing and reading of I2C data, etc.?

Thanks!

Regards,

Daniel Wang

  • 0
    TI__Genius 10300 points

    Hi Daniel,

    Here are a few common situations leading to abnormal I2C communication:

    1. Incorrect bus pull up resistors

    2. Clock stretching ( holding clock line low to delay communication)

    3. Noise and signal interference  - ensure proper grounding

    4. Mismatched voltage levels - host and device must share a compatible voltage level (3.3 or 5V)

    5. Incorrect or unsupported I2C clock speed

    6. SDA/SCL line stuck low - if a transaction fails, SDA/SCL lines may be held low, to clear it, issue a series of clock pulses on SCL to restart the device

    7. Extreme temperatures can affect I2C bus line communication



    Best,
    Mallika Senthil