• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 46 subscribers
  • Views 218 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.

INA226EVM: I2C Communication Issue with INA226 on S32K31EVB Board

santhosh kumar
Prodigy 20 points
Part Number: INA226EVM
Other Parts Discussed in Thread: INA226

Tool/software:

Hello Team,

I am using the S32K31EVB Board and have configured the I2C lines for LPI2C0 to communicate with the INA226 IC. I am encountering an issue where the slave device is not sending an ACK the address byte.

Here are the details of the issue:

  • The first address byte sent over SDA matches the value specified in the INA226 datasheet (0x40).
  • The INA226 IC is not sending an ACK signal in response to the address byte.
  • I have verified the following:
    • The voltage supplied to the INA226 IC is correct.
    • Continuity for SDA, SCL, and GND lines is intact.
  • Pull-up resistors for SDA and SCL are properly connected and within specification.

Despite these checks, the issue persists. Could you please provide guidance on resolving this issue or any additional steps to debug further?

Steps Already Taken:

  1. Verified the voltage to INA226 IC.
  2. Checked the continuity of SDA, SCL, and GND pins.
  3. Confirmed the address byte on SDA matches the datasheet and verified with oscilloscope.                                                                                         

Looking forward to your assistance.

Best Regards,
Santhosh Kumar

  • 0
    TI__Mastermind 26485 points

    Hello Santhosh,

    It's hard to say for sure, but it looks like you may be having some I2C timing issues. From this timing diagram:

    It looks like your t_HDDAT might be too small, as it looks like your clock and data transition at the same time. Try adjusting this timing and see if that works.

    If that does not solve the issue, then I recommend checking the other timing requirements to make sure you are within spec. Similarly, it would be good to confirm the logic levels (especially logic low levels) to make sure that data is being communicated properly.

    Also, when connecting the MCU to the INA226, make sure that the GNDs are shared also. 

    If you are still having trouble after this, then you may want to try testing with the MCU that comes with our EVM to rule out issues from your MCU. That can be found here: https://www.ti.com/tool/TI-SCB. It pairs with this EVM: https://www.ti.com/tool/INA226EVM, but you could jumper it over to your INA226 and still test with our MCU/GUI. 

    Regards,

    Mitch