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: Errors with EVM and GUI

Part Number: TPS65987D
Other Parts Discussed in Thread: TPS6598X-CONFIG, TPS65987

USB PD team,

A customer is trying to connect the TPS65987EVM.

He's following guidance from this document: http://www.ti.com/lit/ug/slvub60b/slvub60b.pdf and using GUI version 5.13.

He's trying to set it up for UFP DisplayPort Mode.  He's seeing the following errors.  Can you help with what might be going wrong?

 

1)      The first thing I try to do is make sure I have connection between the GUI the eval board. To do this I go to the device tab and click on “import settings from device”.  The “Import Configuration from Device” pops up.  For the USB to I2c Adapter I choose FTDI. I2C address is 0, matching switch S4 setting on eval module, S1,S2, and S3 all off. 

If I click on the “Test Read (Mode Register 0x3) I get exeption encountered, with the exception message

Exception Encountered during I2C Test Read:*** ERROR in FTDI call (I2C_DeviceWrite), status: 2

<type 'exceptions.Exception'>

However if I click on the OK button I get another pop up menu that says “Sucessful Import from Device to: Global Device Settings Tab”.

So it seems like I’m talking to the device OK, but Im not 100% sure since the “Test Read” fails.

 

2)      The second thing I try is to load a new project with a default template. I chose the TPS65987DDH  device, standard template, UFP Only, and None( DisplayPort Only). Then select the device tab, then “Export settings to Device (RAM Only)”. The “Import Configuration from Device” pops up.  For the USB to I2c Adapter I choose FTDI. I2C address is 0, matching switch S4 setting on eval module, S1,S2, and S3 all off. I hit OK and get the same exeption error as above,

Exception Encountered during I2C Test Read:*** ERROR in FTDI call (I2C_DeviceWrite), status: 2

<type 'exceptions.Exception'>

Thanks,

Darren