• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 301 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.

TUSB320LAI: Responding on Wrong I2C ADDR 0X47

Suhant Raval
Prodigy 30 points
Part Number: TUSB320LAI

Tool/software:

Hi, There,  

 

We are using, TUSB320LAIRWBR in our product. 

Our product is matured and in production for last two years.  

Out of few thousands board on one of the board I am seeing below observation.  

Even H/W programming for I2C address for TUSB320LAIRWBR is 0x67, it is not responding on this address but it is responding on 0x47. 

------------------ 

Response from Faulty board responding on 0X47 I2C address,  

-------------------------- 

i2cdetect -y 17 

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 

00:          -- -- -- -- -- -- -- -- -- -- -- -- --  

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

40: -- -- -- -- 44 -- -- 47 -- -- -- -- -- -- -- --  

50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

60: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --  

70: -- -- -- -- -- -- -- --              

 

root@MK6:~# i2cget -f -y 17 0x67 

Error: Read failed 

root@MK6:~# i2cget -f -y 17 0x47 

0x30 

root@MK6:~# i2cget -f -y 17 0x47 0x01 

0x32 

root@MK6:~# i2cget -f -y 17 0x47 0x02 

0x33 

root@MK6:~# i2cget -f -y 17 0x47 0x03 

0x42 

root@MK6:~# i2cget -f -y 17 0x47 0x04 

0x53 

root@MK6:~# i2cget -f -y 17 0x47 0x04 

0x53 

root@MK6:~# i2cget -f -y 17 0x47 0x05 

0x55 

root@MK6:~# i2cget -f -y 17 0x47 0x06 

0x54 

root@MK6:~# i2cget -f -y 17 0x47 0x07 

0x00 

root@MK6:~# i2cget -f -y 17 0x47 0x08 

0x00 

root@MK6:~# i2cget -f -y 17 0x47 0x09 

0x20 

root@MK6:~# i2cget -f -y 17 0x47 0x0A 

0x00 

root@MK6:~# i2cget -f -y 17 0x47 0xA0 

0x02 

 

root@MK6:~# i2cget -f -y 17 0x47 0x45 

0x00 

------------------ 

Response from OK board responding on 0X67 I2C address,  

------------------ 

root@MK6:~# i2cdetect -y 17 

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 

00:          -- -- -- -- -- -- -- -- -- -- -- -- --  

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --  

50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  

60: -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- --  

70: -- -- -- -- -- -- -- --                          

root@MK6:~# i2cget -f -y 17 0x67 

0x00 

root@MK6:~# i2cget -f -y 17 0x67 0x01 

0x32 

root@MK6:~# i2cget -f -y 17 0x67 0x02 

0x33 

root@MK6:~# i2cget -f -y 17 0x67 0x03 

0x42 

root@MK6:~# i2cget -f -y 17 0x67 0x04 

0x53 

root@MK6:~# i2cget -f -y 17 0x67 0x05 

0x55 

root@MK6:~# i2cget -f -y 17 0x67 0x06 

0x54 

root@MK6:~# i2cget -f -y 17 0x67 0x06 

0x54 

root@MK6:~# i2cget -f -y 17 0x67 0x07 

0x00 

root@MK6:~# i2cget -f -y 17 0x67 0x08 

0x00 

root@MK6:~# i2cget -f -y 17 0x67 0x09 

0x20 

oot@MK6:~# i2cget -f -y 17 0x67 0x0A 

0x00 

root@MK6:~# i2cget -f -y 17 0x67 0xA0 

0x02 

root@MK6:~# i2cget -f -y 17 0x67 0x45 

0x00 

 I attached snip of Schematic  for your referecne.

I verified, R1443 value and it connection going to ADR Pin on board responding on 0X47 I2C address. 

It is As per OK board. Also On Multimeter ADR Pin sees 3.3VDC as Pull up. 

Also R1446 is Not FIt on Board on board responding on 0X47 I2C address. 

I attached I2C clk and data waveform  board responding on 0X47 I2C address and board responding on 0X47 I2C address. I don’t see any corruption on these waveform. 

 ----------------

Can you please let me know,  

Am I missing something to verify ?  

Why this particular Piece of TUSB320LAIRWBR is responding on on 0X47 I2C address? 

Has some one reported such issue to you? What was resolution given ?  

What next course of action you suggest to us ?  

Or do you need more information ?  

-------------

 Thanks, 

Suhant. 

-------------

  • 0
    TI__Mastermind 30090 points

    Hi Suhant,

    Given that your design is already in production, I recommend submitting the device-in-question to TI's customer product return process. The E2E platform is primarily for supporting designs in the concept and validation phases.

    Best,

    Shane

  • 0 in reply to Shane Hauser
    Prodigy 30 points

    Hi, Shane, 

    Sorry, I dont understand.

    Do you mean it is TUSB320LAIRWBR part manufacturing/ supply issue ? 

    did Texas observed/ got reports from customer for such issue ? 

    Can you please reply, my query here ? 

    if it is required, my purchase team will contact, TI customer product return.

    My intention to know technically, what is wrong with this particular piece ? 

    Hope you understand.

    Thanks,

    Suhant

  • 0 in reply to Suhant Raval
    TI__Mastermind 30090 points

    Hi Suhant,

    We are not aware of any issue with the TUSB320LAI reading on the wrong I2C address as you describe. Are you certain that the voltage at the ADDR pin is within the high input range on your failing boards?

    Furthermore, how many units do you see this behavior on/how often do you see this behavior?

    If you confirm that the ADDR voltage is correct, then we will likely need internal testing on the device to determine the root cause of this behavior. The customer return process is our method to perform this testing when a customer design is in production.

    Best,

    Shane

  • 0 in reply to Shane Hauser
    Prodigy 30 points

    Hi, Shane, 

    Thanks for reply.

    Please find my reply below.

    Are you certain that the voltage at the ADDR pin is within the high input range on your failing boards? - Yes.

    Furthermore, how many units do you see this behavior on/how often do you see this behavior? - ATM, 1 in 1000 Board.

    Now, it make sense to me, about customer return process.

    I will update you my action item in next 3-4 days

    Thanks,

    Suhant

  • 0 in reply to Suhant Raval
    TI__Mastermind 30090 points

    Sounds good Suhant.

    Best,

    Shane

  • 0 in reply to Shane Hauser
    Prodigy 30 points

    Hi, Shane, 

    We decided to follow path of contacting via customer return process. 

    Thanks for all support and time.

    Suhant