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: Possibility to control USB3.2 MUX through GPIO without I2C interface?

Part Number: TUSB320LAI
Other Parts Discussed in Thread: TMUXHS4212, TPS25821, TUSB321AI, ESD441

Tool/software:

Hi Team,

Customer wants to replace an USB OTG interface with USB-C DRP (USB3.2 up to 1.5A) and use the TUSB320LAI for this use case.

Can I kindly ask you to clarify whether it is possible to control TMUXHS4212 through an GPIO Pin of TUSB320LAI when there is no I2C interface?

Or is the TPS25821 better suited for this use case?

Looking forward to you feedback.

Best Regards,

Gizem

  • Hi Gizem,

    The TUSB320LAI does not have a GPIO pin for controlling a USB3 MUX. If you need this functionality from one of our CC controllers, consider the TUSB321AI. The TUSB321AI has a DIR output made to control USB3 MUXes like the TMUXHS4212.

    My team only supports our TUSB32x CC controllers, but I'm looking at the datasheet for TPS25821 and it seems this device only supports DFP mode. If you want a DRP port I'm not sure TPS25821 would work.

    Best,

    Shane

  • Hi Gizem,

    You asked the follow up question: Is it possible to implement USB OTG with recommended TUSB321AI?

    Yes, you can implement OTG with the TUSB321AI. You can configure the device in DRP mode and connect the ID pin to the OTG USB controller to determine whether you are the host or device. This would be similar to the following description from the TUSB320LAI datasheet:

    Best,

    Shane

  • Hi Shane,

    Customer shared a schematic draft for TUSB321AI and HD3SS3212x with me. Can yo support a schematic review?
    However, I would prefer sending the customer schematics as an email.
    Looking forward to your feedback.

    Best Regards,

    Gizem

  • Hi Gizem,

    I can review the schematic for these devices. Can you please direct message the schematic to me over E2E?

    In general, Its our groups policy to keep all support on E2E rather than use email. You can direct message me by accepting my friendship request on E2E:

    Best,

    Shane

  • Hi Shane, 

    Sure, I just did send you a direct message with the schematic attached.

    Many thanks for looking into this.

    Best Regards,

    Gizem

  • Hi Gizem,

    I have a few comments on the schematic:

    1. I recommend using size 0201 capacitors on the TX lines instead of 0402. Size 0402 capacitors are larger than the high speed trace and can be a source of signal reflections:

    2. I recommend removing the Common mode chokes on the RX1 and RX2 lines. Typically these are unnecessary and can add signal reflections to the trace. If you do want to keep these, ensure they support the signal speed you plan to use.

    3. Is the ESD protection integrated into the common mode chokes? I want to be sure you have ESD protection between the 3212 and the type-C connector. Can you provide the part number of the ESD protection?

    4. Use a 1K pulldown on CURRENT_MODE on the TUSB321AI instead of direct connecting to GND.

    5. I recommend using ESD441 on the CC1/CC2 lines for ESD protection if this is a concern.

    Let me know if you have any questions.

    Best,

    Shane

  • Hi Shane,

    There is one more question from customer: 

    The VBUS_DET of TUSB321AI does have a series resistor with 900k 1% tolerance. In customer system they do have a 909k 1% series resistor in 0603 package.

    Does the resisitor need to be 900k 1% or is 1M also possible?

    Can I kindly ask for your feedback on this?

    Many Thanks,

    Gizem 

  • Hi Gizem,

    From the datasheet, the resistor between VBUS_DET and the VBUS needs to be between 855Kohms and 920Kohms:

    1M would be too much resistance and may interfere with the CC negotiation on the type-C port.

    Best,

    Shane