• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 537 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.

Original question:

TUSB320: I2C programming issue

TUSB320LAI: I2C ADDR H setting

Elisha Tarroza71
Expert 3700 points
Part Number: TUSB320LAI
Other Parts Discussed in Thread: TUSB320

Hello,

A customer we are supporting at the CSC is having problems with the I2C of TUSB320LAI.
This is a bit similar to this post: https://e2e.ti.com/support/interface/f/138/t/700116?TUSB320-I2C-programming-issue


It seems that the datasheet of TUSB320 (http://www.ti.com/lit/ds/symlink/tusb320.pdf) has already been updated to 0x61

For the newer TUSB320s (-LAI, -HAI, -HI, -LI) however, it's 0x67:

Just confirming -- is this a typo on the TUSB320LAI/HAI/HI/LI's datasheet? Should it be 0x61 as well?

Thanks!

  • 0
    TI__Guru 64326 points

    Hi,

    No, The values listed in TUSB320LAI/HAI/HI/LI should be correct (0x67/0x47). Only TUSB320 has I2C address (0x61/0x60). This is for ADDR = (H/L).

  • 0 in reply to Malik Barton57
    TI__Expert 3700 points

    Hello Malik,

    I see the commands for these are indeed different. Thanks a lot for the clarification. 

    However, the customer is having intermittent I2C communication issues. They are also having problems reproducing this communication issue.
    So they tried using 0x61 for -LAI as well, and it works according to him.

    I do see in his schematic that there is a 200k external pull-up at the ADDR pin. Could this be the reason why the I2C can sometimes still communicate regardless of the ADDR setting?

    Also, can I share with you their schematic privately? We need help in checking the cause of the intermittent I2C connection they are experiencing.

    Thanks a lot for your support.

  • 0 in reply to Elisha Tarroza71
    TI__Guru 64326 points

    Hi,

    Can you ensure the customer has the correct device soldered down / EVM? LA marking should be the top marking on packag. Your customer may be accessing other devices on the I2C bus unless TUSB320LAI si the only device on the bus. You could reccomend shorting ADDR to ground or through a 1k pull down. Is the customer following the guidance in sections 8.3.1 TUSB320LA Initialization Procedure and 7.4 Programming (if they are using a custom I2C host)?

  • 0 in reply to Malik Barton57
    TI__Guru**** 152510 points

    Elisha:

       any update?

  • 0 in reply to Brian Zhou
    TI__Expert 3700 points

    Hello Brian,

    I had no response from the customer after two emails. Perhaps we can close this thread now.

    Thank you for your support.