• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 33 subscribers
  • Views 489 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: About differences between the following parts

Hide
Guru 21045 points
Part Number: TUSB320LAI
Other Parts Discussed in Thread: TUSB320LI, TUSB320

Hi Team,

 

Our customer would like to use TUSB320LAI but this device is out of stock.

Therefore, their choices are TUSB320 and TUSB320LI.

 

I refer to the following E2E thread and have some questions.

https://e2e.ti.com/support/interface-group/interface/f/interface-forum/707926/tusb320-what-are-the-differences-between-the-following-parts-tusb320-tusb320li-tusb320hi-tusb320lai-tusb320hai

 

------

[Q1]

Feature: Current Detection through GPIO

TUSB320: Yes. Can't detect change in current advertisement unless cable removal/insertion

TUSB320LI:Yes

TUSB320LAI:Yes

 

I understand that TUSB320LI and TUSB320LAI can detect change in current advertisement but USB320 can't detect change.

Is my understanding correct?

If correct, where is this mentioned in the datasheet?

------

 

[Q2]

Feature: Current Detection through I2C

TUSB320: Yes, requires software workaround to detect change in current advertisement.

TUSB320LI:Yes

TUSB320LAI:Yes

 

I understand that TUSB320LI and TUSB320LAI can detect change in current advertisement without external control but TUSB320 need external control(software workaround).

Is my understanding correct?

If correct, where is this mentioned in the datasheet?

And, could you please let us know about software workaround of TUSB320?

------

 

[Q3]

Feature: Directed to Disabled State

TUSB320: No

TUSB320LI:Yes

TUSB320LAI:Yes

 

I understand that TUSB320LI and TUSB320LIA have “DISABLE_UFP_ACCESSORY” and “DISABLE_TERM” but TUSB320 don’t have those.

Does " Feature: Directed to Disabled State" indicate this difference?

------

 

[Q4]

Feature: DFP waits for VBUS below VBUS_DET threshold before transitioning from AttachWait.SRC to Attached.SRC

TUSB320: No

TUSB320LI:Yes

TUSB320LAI:Yes

 

I understand that content  of “VBUS_DET IO Pins (Connected to System VBUS signal)” and “VBUS Detection” are same in each device datasheet.

So, I can't understand the difference between "No" and "Yes".

Could you please let us know the difference and detail information?

------

 

Regards,

Hide

  • 0
    TI__Guru*** 146095 points

    Q1:  its not mentioned in datasheet

    Q2:  When operating in I2C mode, the TUSB320 device uses the SCL and SDA lines for clock and data and
    the INT_N pin to communicate a change in I    2C registers, or an interrupt, to the system. The INT_N pin is
    pulled low when the     TUSB320 device updates the registers with new information. The INT_N pin is open
    drain. The INTERRUPT_STATUS register should be set when the INT_N pin is pulled low. To clear the
    INTERRUPT_STATUS register, the end user writes to I2Cc

  • 0 in reply to Brian Zhou
    TI__Guru*** 146095 points

    Q3: UFP accessory and Directed to Disabled are different , but both were not implemented in the original TUSB320.

    Q4: A DFP upon a removal must discharge VBUS.  The TUSB320 will wait until VBUS is removed before it will assert the ID pin.

  • 0 in reply to Brian Zhou
    Guru 21045 points

    Hi Brian-san,

     

    Thank you for your prompt reply.

    I have additional questions for [Q3] and [Q4].

     

    ------

    [Q3’]

    I understand that both(“DISABLE_UFP_ACCESSORY” and “DISABLE_TERM”) were not implemented in the original TUSB320.

    However, I can’t understand your comment that UFP accessory and Directed to Disabled are different.

     

    I guess that "Feature: Directed to Disabled State" means " DISABLE_TERM " only.

    Is my understanding correct？

    ------

     

    [Q4’]

    I understand that TUSB320 have to wait until VBUS is removed before it will assert the ID pin.

    However, TUSB320LI and TUSB320LAI don’t need wait time so these devices are better than TUSB320.

    Is my understanding correct?

    ------

     

    Regards,

    Hide

  • +1 in reply to Hide
    TI__Guru*** 146095 points

    Q3: you are right.

    Q4: sorry,   CC spec is CC device need to wait until VBUS is removed before it will de-assert the ID pin. TUSB320 is no , which means it didn't follow CC spec.

    Regards

    brian

  • 0 in reply to Brian Zhou
    Guru 21045 points

    Hi Brian-san,

    Thank you very much for your help.

    Regards,

    Hide