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.

TUSB216IEVM: How to process D1P and D2P in case of CDP use

Part Number: TUSB216IEVM
Other Parts Discussed in Thread: TUSB216I,

Hi team,

Customer uses TUSB216I to compensate signal quality and they need to use CDP.

Figure8-1 of the datasheet shows D1P and D2P (D1M and D2M as well) are shorted with CDP disabled and they are also shorted on the EVM.
I found the E2E but there are no statement about CDP on the E2E, datasheet and user guide of the EVM.

Could you share how to process the pins when they want to use CDP?
Does D1P and D2P have to be shorted always regardless how customer use?

Best regards,
koyo

  • Hello Koyo,

    Yes, the D1P and D2P are always shorted for the TUSB216I device.  (The D1M and D2M pins are always shorted as well).

    CDP mode is designed to work with the pins shorted.  On the TUSB216IEVM, the CDP_ENZ pin on the 6x2 header can be held low by jumpering the pin to a ground next to it to enable CDP mode.  Once enabled, on the next device connection event you will be able to see the CDP handshake occur on the USB bus before the HS handshake.  Please be aware that CDP charging mode can draw up to 1.5A, it may be necessary to externally power the EVM to account for this if CDP mode is being tested.  If the EVM is being externally powered through pin1 of the 6x2 header, then the 0 ohm resistor connection the upstream VBUS to the EVM power should be removed to prevent back driving voltage on VBUS.

    Let me know if you have any further questions.

    Regards,

    JMMN

  • Hi JMMN,

    Thanks for the answer, I understand D1P and D2P are always shorted regardless of a situation.

    Let me ask another question.
    The Vcc range is 2.3V to 6.5V.
    Is there any different operation depending on the input?
    (e.g. have to connect to VBUS)

    Best regards,
    Koyo

  • Hello Koyo,

    Redriver behavior is the same across the VCC range.  

    Regards,

    JMMN