• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 879 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.

TPS65987EVM: TPS65987EVM Application Customization Tool Issues

Shea Ako
Prodigy 65 points
Part Number: TPS65987EVM
Other Parts Discussed in Thread: TPS65987, TPS65981, TPS65987DJEVM

Hello,

I have been working with the TPS65987EVM, considering the TPS65987 for our design. I have been having a lot of issues with the Application Customization Tool, primarily in debug mode, and am wondering if others experience the same issues, or if there is a known workaround.

In general, reading and writing over I2C (via FTDI interface) is very unreliably. Reading configuration registers and sending commands seems to work about 40% of the time. Often times reading configuration registers populates the UI with garbage values (both manual and polling) or does not respond at all. I am unable to confidently verify that writes to configuration registers are "taking". Sending commands (e.g. SSrC - Send Source Capabilities) often returns SUCCESS_CMD with no corresponding data sent over PD, monitored with a protocol analyzer. When things start getting flakey, usually exiting debug mode and re-plugging the FTDI interface cable fixes things, for a period of time.

Using FTDI's CDM Uninstaller utility I've tried removing and then re-installing the drivers packaged with Application Customization Tool installer, which notably are not the most recent version of the FTDI drivers. I also tried the most recent version of the drivers, published on FTDI's website, which didn't work at all. I guess there's a reason that the Application Customization Tool installer comes packaged with an older version. I've also tried rebooting, and everything else I can think of that might fix things, without success.

Thankfully, updating the SPI flash seems to work reliably, with one exception. Attempting to "Re-flash EVM Firmware (Recovery)" with the tps65987_evm_flash_image.bin fails with the following message:

Exception Encountered during EVM Recover:hw_spi_flash_erase failure: attempting to erase to null handle

<type 'exceptions.Exception'>

 

I am using:

TPS65981_2_6_7_8 Application Customization Tool

GUI Version : 6.1.1

Date of release : 10th October, 2019

Windows 10, version 1903.

Any help or advice would be greatly appreciated.

Being able to address the host interface directly from the Application Customization Tool would greatly help us to evaluate the appropriateness of the TPS65987 for our design.

TIA

 

  • 0
    TI__Mastermind 30000 points

    Hello Shea,

    Unfortunately, you have already done the few things that I would recommend to have a more reliable connection with the FTDI device. As you have noticed, the communication with the FTDI device is not always reliable which is why we have moved away from it with future EVMs.

    You can still use debug mode to read the registers and write 4cc commands, but I would read the I2C channel using a logic analyzer to make sure that the messages are sent correctly, referring to the host interface technical reference manual. 

  • 0 in reply to Adam Mc Gaffin
    Prodigy 65 points

    Hi Adam,

    Thank you for your response. A couple more questions:

    Would you recommend using an Aardvark interface? Is there an adapter board available that breaks out the expansion connector to more easily accessible pins? Or is my best bet to hack my own header onto the TPS65987EVM board, to reliably access the I2C interface?

    Or perhaps I should have purchased a TPS65987DJEVM, which has a built in TIVA interface?

    What's your best recommendation for evaluating the TPS65987 and developing flash images with the Application Customization Tool, outside of developing our own integrated solution?

    Thanks,

    Shea

  • 0 in reply to Shea Ako
    TI__Mastermind 30000 points

    Hello,

    I would not recommend using the TPS65987DJEVM as this is a different device that is geared towards host thunderbolt platforms. 

    You could use an Aardvark as that is a tried and true method for I2C interaction. You can also use the aardvark to flash binary images directly to the SPI flash once you have your own system. You can buy a split cable adapter that will break out the signals for the Aardvark. The flash center program lets you program directly to the flash. 

    https://www.totalphase.com/products/split-cable/

    https://www.totalphase.com/products/flash-center/ 

  • 0 in reply to Adam Mc Gaffin
    Prodigy 65 points

    Thanks, Adam.

    I ended up adding my own header, tacked onto the pads for R6, R8, R10, to access the I2C1 interface. I am now able to reliably access the device's I2C host interface.

    An entry for the suggestion box:
    Including an adapter board that breaks out the Samtec mezzanine expansion connector to 0.1" headers would make evaluation of your products easier, FTDI issues notwithstanding. For example, this would support the connection of the Aardvark split-cable that you referenced, as well as other prototyping and evaluation tasks, without potential customers needing to solder their own connectors onto 0402 resistor pads of the EVM.

    Thanks for your help,

    Shea