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.

TPS65981: Source of ID signal for TUSB1210

Part Number: TPS65981
Other Parts Discussed in Thread: TUSB546-DCI, , TUSB1210, HD3SS3220

Hi,

I am using a TPS65981 for PD and CC control for a USB Type-C connector (with USB 2.0 and 3.1 Gen 1). The superspeed mux I'm using is the TUSB546-DCI.

I'm going to connect the USB 2.0 D+ / D- signals to the TUSB1210 to interface with my CPU via ULPI. My question is: what do I do with the ID signal needed by the TUSB1210? Can this be sourced from the TPS65981 somehow?

Thanks!

  • Hi inve7,

    For OTG applications, the ID (identification) pin is connected to the ID pin of the micro-AB receptacle. ID detector indicates if micro-A or micro-B plug is inserted.

    As defined in USB 2.0 Specification Rev. 1.3 OTG section, the ID pin dictates the initial role of the plug event. If ID is high, then assume a peripheral role. If ID is low, then assume a host role.

    what are you using the ID pin for?
    note: the datasheet states: If unused Leave input floating or TUSB1210 is Device mode only. Tie to GND through RID < 1kOhm if Host mode.

    Thanks

  • Hi Jeff,

    Yes, that's exactly what I'm using the ID pin for...To indicate to the TUSB1210 whether it should act as host or device for OTG functionality. However, we are not using a micro-AB receptacle in our application. We are using a type-C connector which has no ID pin.

    In other TI devices with CC logic, such as the HD3SS3220, there is an output that mimics the ID pin. But, the TPS65981 doesn't have this ID output.

    I think I may have answered my own question though ;-) Is the proper solution to program one of the TPS65981 GPIO signals to use the "UFP_DFP" GPIO Event and connect that to the TUSB1210 ID input?

    Thanks!
  • Hi inve7,

    Thanks for the clarification, good to have sparked a solution for you.

    Your proposed solution is correct. The 81 is capable of a "UFP_DFP" GPIO event. Use the config tool for this (see screen shot below for clarification).

    note: the GPIO event maps UFP as low logic which is opposite from ID  

    Thanks

  • Hi Jeff,

    Thank you for confirming this! There seems to be a discrepancy about the polarity of the UFP_DFP event though. In the "TPS6598x GPIO Events" app note it states:

    UFP_DFP

    Asserted high when data role is UFP or no connection at Type-C port

    Asserted low when data role is DFP

    But as you mentioned, the customization tool shows UFP (0) / DFP (1).

    Which is correct?

    Thanks!

  • Hi inve7,

    Sorry for this confusion. I did a simple test to figure which one is correct. When I config a UFP only and look at GPIO status in the host GUI I see that my GPIO_0 is high. Therefore the app note is correct.

    I will update the GUI team to change this accordingly.
    Let me know if you have any other questions.
    Thanks!
  • Hi Jeff,

    Thank you for checking and verifying this so quickly! That should settle everything :-)

    Thanks!
  • Hi inve7,

    I hope so! Still, Please let me know if you have ANY more questions!

    Thanks