• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 4 answers
  • Subscribers 32 subscribers
  • Views 186 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.

Original question:

TUSB320: TUSB320 ID keeps oscillating

TUSB320: comparison with WUSB3801Q12TR

Naizeng Wang
Expert 4780 points
Part Number: TUSB320
Other Parts Discussed in Thread: TUSB321,

Hi team.

I think TUSB320 is p2p with WUSB3801Q12TR, could you please share the spec comparison table? Thanks! 

Nison 

  • 0
    TI__Mastermind 22185 points

    Hi Nison,

    I couldn't find the datasheet for the WUSB3801Q12TR online. Using the TI cross reference tool, I see the TUSB321 is a drop-in replacement.

    This means the TUSB321 is pin to pin and has the same functionality as that device.

    Best,

    Shane

  • 0
    TI__Mastermind 22185 points

    Hi Nison,

    Thank you for sharing the datasheet. You are correct that the TUSB320 is pin to pin with that device. I recommend using the TUSB320LAI, which is a newer version of the TUSB320.

    The 320LAI has a lower current draw than the original 320 (100uA --> 70uA in UFP mode) and the ID pin is failsafe.

    Here's a table on the differences I saw between our device and the one you are referring to:

    TUSB320LAI WUSB3801Q12TR
    I2C Address options 0x67(H), 0x47 (L) 0x68 (H), 0x60 (L)
    OUT2/OUT1 state at no connection No connection at 2b'11 No connection at 2b'01
    VDD supply range 2.7V - 5V 2.7 - 5.5V
    EN_N High voltage level (VDD-0.3) - VDD 1.15V<
    Active current while unattached 70uA 22.5uA

    I hope this helps, let me know if you have any questions.

    Best,

    Shane

  • 0
    TI__Mastermind 22185 points

    Hi Nison,

    Following up here on your latest question from email:

    "I found that the I2C address is different so customer has to change code to make them compatible. Do we have device with the same address?"

    The original TUSB320 shares one I2C address with the part you've sent. Both parts have I2C address 0x60 when the respective ADDR pin is low.

    TUSB320 WUSB3801Q12TR
    I2C Address options 0x61 (H), 0x60 (L) 0x68 (H), 0x60 (L)

    I looked at our other parts and we don't have another CC controller that shares I2C addresses with the WUSB3801Q12TR.

    Best,

    Shane

  • 0 in reply to Shane Hauser
    TI__Expert 4780 points

    Hi Shane,

    Customer cannot use TUSB320 because in some application, they will pull address pin to high, so the address is different from each other. Could we make a spin device with 0x68 (H), 0x60 (L) address? 

  • 0 in reply to Naizeng Wang
    TI__Mastermind 22185 points

    Hi Naizeng,

    Unfortunately we can't make a spin for that purpose.

    Best,

    Shane

  • 0 in reply to Shane Hauser
    TI__Expert 4780 points

    Hi Shane,

    Is there any other device who are p2p with us with same address? If so, we will try to convince customer of introducing both our device and this competitor's device. 

    Nison

  • 0 in reply to Naizeng Wang
    TI__Mastermind 22185 points

    Hi Nison,

    I'm unsure about p2p competitor devices that share the same address. Let me reach out to our PME and see if he has any ideas.

    Best,

    Shane

  • 0 in reply to Naizeng Wang
    TI__Mastermind 22185 points

    Hi Nison,

    Our PME isn't aware of other p2p parts with the TUSB320, so I'm not sure how much I can help with competitor options.

    I informed our PME about the WUSB3801Q12TR as a p2p competitor. If there's any questions you have on the TUSB320 itself I'm happy to answer.

    Best,

    Shane