• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 33 subscribers
  • Views 337 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.

TPS65987D: Testing custom PCB with TPS65987EVM

Dylan Johnson
Prodigy 20 points
Part Number: TPS65987D

Hello,

We're attempting to test a TPS65987DDH chip on a custom PCB and having a bit of trouble getting an established USB contract going. We're using a TPS65987EVM as the DFP port to test power delivery. The custom PCB has sink PDOs of the default 5V/0.9A and our target PDO of 20V/3A.

The issue we're running into seems to be showing similar behavior to when we were testing two separate EVMs. The source device had its LEDs blink periodically every second or so (5V PDO LED, SSMX FLIP & USB3 LEDs). The issue previously was that the source PDOs weren't setup properly, but we've tested a sink and source EVM without issue now.

Would there happen to be any issues with the attached project files?

TPS65987EVM (Source):
TPS65987DDH_EVM_DFP_Adv.pjt

Custom PCB with TPS65987DDH chip (Sink):
ct-config.pjt

  • 0
    TI__Genius 12700 points

    Hi Dylan,

    I will take a look at the pjt file and provide some feedback by the end of the week.

    Thank you,

    Hari

  • 0
    Prodigy 20 points

    Hi Hari,

    Thank you for taking a look into the project files, though I think we might have found the main issue. There was a issue with one of the custom PCB parts that had a short that's been resolved. This was causing the periodic blinking effects on the LEDs. There was a separate issue where no contract was being created, but it looks like the resistive divider for ADCIN1 was slightly off. The contract appears to be working as expected now, supplying 20V.

    We're hoping to finish up testing on the Alternate Mode DIsplayPort portion of this PCB, but for the time being this issue has been resolved.

    --Dylan Johnson