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.

USB-C-PD-DUO-EVM: TPS65987D Issues with Programming

Part Number: USB-C-PD-DUO-EVM

I have a custom PCB designed to utilize the reference design from the source side of the USB-C-PD-DUO-EVM. The sink side was not utilized. The PCB is designed to take in 20V at 4 amps from another PCB so this is similar in spec to the DC barrel jack input of the USB-C-PD-DUO-EVM. Note: the source side design was not modified in any way and is exactly as it was designed and laid out in the USB-C-PD-DUO-EVM board. 

I am having a few issues. The first is the board does not do anything when plugged into 20V power and when a USB sink device is plugged into the USB type C connector. The VBus LED stays off but the 3.3V LED and SYS PWR LED turns on. I have verified the TPS65987DDH chip is getting 3.3V at VIN_3V3 and LDO_3V3 pins so the chip is powered correctly. I also see 19-20 V on the PP_HV pin. None of the voltage selection LEDs nor the VBUS LEDs are turning on. I believe this issue may have to do with the chip configuration and that it is not programmed due to being a custom PCB design.

So I downloaded the TPS659xx Application Customization Tool and have followed the instructions in the user manual for the EVM device and at this link: https://e2e.ti.com/support/power-management-group/power-management/f/power-management-forum/1170489/usb-c-pd-duo-evm-usb-c-pd-duo-evm 

However, everytime I select New project > TIDA-050012 Source board and then select Binary > Flash from current project, I get an SPI verification error. However, if I check the I2C and SPI functions through the adapters settings tab, I see the I2C address is 0x20 for the device and that the Mode register reads as "APP", the version is "0xf7071000", and the SPI flash read is "Read Success : array('B', [0,0,0,0])" similar to the results that Sahin Baytekin had in the link above. I can also read the .bin file from another copy of the same custom PCB board with a previously unprogrammed TPS65987DDH chip and then use those project settings to flash to the 1st PCB board. When doing this, it flashes correctly and the SPI verification is successful. 

Do we know what is causing this? As previously stated, this is the same design as the USB-C-PD-DUO-EVM board and was not touched so it should function the same. Also, I noticed the voltage divider for the source TPS65987DDH on the USB-C-PD-DUO-EVM is set to 3.3V with 10K and 100K resistors. This leads to a ADCIN1 voltage of 3.0V which according to table 8-5 in the TPS65987D data sheet is not correct. See Section 8.4 in datasheet here: https://www.ti.com/lit/ds/symlink/tps65987d.pdf?ts=1681862546330&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FTPS65987D

What should be the correct ADCIN1 value if I want to source up to 20V and 4 amps? Why is the ADCIN1 pin set incorrectly in the USB-C-PD-DUO-EVM board design? Is there something I am missing?

Thanks in advance.

  • Hi Tyler, 

    Thank you for reaching out!

    I will look into this and get back to you by the end of the week. 

    Best Regards, 

    Aya 

  • Hi Aya,

    I believe I have figured out the issue:

    In the USB-C-PD-DUO-EVM user manual, the PDF schematics list R43 as DNP but the PDF and Altium Design files for the TIDA-050012 reference design do not. I forgot to list this as DNP as well when sending to the board house and, consequently, the MISO line for the SPI comms to the Nor flash was shorted to ground. I noticed this when monitoring the SPI communication while trying to read & write the binary files to the flash through the Application Customization tool.

    I removed this resistor to ground from one PCB to test with and this fixed the issue. I was able to successfully program the TPS65987D chip using the Source board project files and then plugged an SSD, iPhone, and a laptop in through the USB C connector and can power/charge all three.

    Tyler

  • Hi Tyler, 

    I am so glad to hear that!  Thank you for sharing your insight as it could benefit other community members facing similar issues as well.

    Feel free to open a new thread if you have further questions/issues. 

    Best Regards, 

    Aya