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.

TPS65983B: VConn Not Powering to 5V when using Active Cable

Part Number: TPS65983B

Hello,

I am using TPS65983 Thunderbolt Application Customization 4.10, which uses based image TPS65983A_fw4_0004_59_00.bin

I configured the firmware with only one Source PDO, and it is using External High Voltage Power Path (PP_HVE) for 5V/3Amp power delivery.
I know the external FETs are wired correctly because I can negotiate PD and consume 5V/3A from my device, but when I tried an Active cable. I noticed on the PD analyzer that VConn is not powering to 5V, and therefore the link fails.

Is there a step in the firmware configuration I am missing?

Thank you

  • Hello,

    Can you please tell me which TBT reference design you are following? Please note that the TPS65983B is only approved for use in TBT device reference designs from Intel.

    Thank you,
    Eric

  • Hi Eric,


    My design is based on Apex Creek - Base Reference Design

    but I am only supporting the minimum 5V/3A PD and I want to use the External Power Path as the only PDO.

    Thank you

  • Hello,

    The apex creek design will automatically enable the VCONN path when required by an active cable. Please make sure you are following the reference design exactly and not make any unsupported changes. 

    Thanks,
    Eric

  • Hi Eric,

    I'm aware of the expected behavior. This is not my first Apex Creek design, but this is the first time I am trying to configure the TI controllers to use the external power path as the sole PDO for 5V/3A.

    Are you implying that is not supported? Because that is a customization option in the Application Customization tool. 


    Thank you

  • Hi,

    Yes, this change is outside of what the TPS65983B firmware supports for this reference.

    Changing the 5V source path to the external HV PP requires direct collaboration with Intel and cannot be supported directly.

    Regards,

    Scott