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: difference between our board and EVM

Part Number: TPS65987D
Other Parts Discussed in Thread: TPD6S300A

 

 we have two TPS65987D. One of them is shall sink 20V 3A starting from dead battery. I have connected ADCIN1 to a 130k/100k voltage divider (DIV=0.43) and a pulldown on the MISO line. This should make the PD-controller to select BP_NoWait and Configuration 3. Connecting an USB-C cable to a power source that can deliver 20V 3A gives only 5V. Doing the same thing with a TPS65987-90 Evaluation Module gives 20V. (S4 sw5 on, and pressing S3 while connecting the USB cable.)

There are two differences in the designs:

1) On our board there is a TPD6S300A for protection, 

2) On the Eval-board the PD-controller is PTPS65987D, on our board is a released TPS65987D.

Is there any difference between the two versions of TPS65987D that can explain the different behavior?

 

Connecting USB cable to our Board gives 5V 0.10A. (Packet 18: Request Obj Pos 1.)

 

Connecting USB-cable to TPS65987-90 Eval Module while pressing S3 gives 20V 3A. (Packet 22: Request Obj Pos 6.)

Is there anything we can try? we have two TPS65987D.docx

 

  • Hi Alan,

    I have assigned this thread to the appropriate engineer, he should get back to your question tomorrow.

    Thank you,
    Eric

  • Hi Ajayt,

    How have you designed your TPS65987D? I would take a look at the Layout section on the datasheet which shows an example.

    Also, do you program the same configurations to both TPS65987D PD controllers? Can you share your GUI configuration project files?

    From my understanding, you are connecting a power source to one PD controller and then sinking power into the other PD controller using an EVM. Is that correct?

    Thank you,

    Hari

  • I have made some more tests. We have two different Eval boards for TPS65987D. The tests below I made with the TPS65987-90 Evaluation Module. Now I have made the same test with the USB-PD-Duo EVM, (with TPS65987D DH). I had to make a small modification to configure it for the Default Configuration 3. The result was the same as for our board, it selected 5V from the source; not 20V as expected. With the Application-Customization tool I saw that the reason for this was that in the register #37 Autonegotiate Sink was not enabled. When I checked this box and sent the command Get Source Capabillities, 20V was selected.

     

    The conclusion is that there is a difference between the PTPS65987D DH and the released TPS65987D DH regarding this, and TPS65987D DH can not be used for sinking higher voltage than 5V without the use of an external flash or configuration via I2C. What is your comment about this?

     

  • Hi Ajayt,

    Your analysis looks correct. I would suggest using an SPI Flash for your configuration or using an embedded controller to update the necessary fields during run-time via I2C. 

    Thank you,
    Eric 

  • HI Eric :-

    Since the board is powered up from dead battery we have no controller available. The only option is to use an SPI Flash. How do we create a file that can be flashed?

  • Hi Alan,

    You can download the TPS6598x Application Customization Tool and create your configuration image. Once you have completed selecting your settings, you can select Binary --> Save Full Flash Binary to save the image you will load onto the SPI Flash.

    Thank you,
    Eric

  • Thanks for this, also :-

    On the board We have a second USB port with a second TPS65987DDH. This can be configured by the CPU. With the Application Customization Tool I have made a configuration. How can this configuration be exported to the processor c. code?

     

    How is the over current clamp configured with the Application Customization Tool? According to the datasheet page 9, 20 different levels can be selected.

     

  • Hi Alan,

    The .C file can be exported from the Application Customization Tool by selecting: Binary --> Save Binary and then select .C Array declaration for the Save File Format. You would need to use the Low Region image for the SPI-less boot image from the CPU.

    In terms of adjusting the over-current clamp position, it is covered in page 8 of the following app note: http://www.ti.com/lit/an/slva994/slva994.pdf

    Thank you,
    Eric