TPS65981: TPS6598x, Application Cutomization tool, FTDI

Eric,

Thank you for your reply.
I can see the same error message as follows when I tried to access using Host Interface Tool.
"No FTDI I2C channels (I2C_GetNumChannels) detected, exiting...."
I2C address is 0x3F when I executed I2C scanner using Aadvark.
So, I think that FW is correctly booted.
I tried to flash the FW to device based on the following procedure.
1. Connect Aadvark to FDTI board
2. Run Application Customization tool ver 2.10
3. Read project file, "TPS65981_HD3SS460_UFP_FULL_2_10.tpl"
4. Execute [Device]->[Flash App firmware to Device]
5. Select "Aadvark" for "USB to SPI Adapter"
6. Push [OK] button
7. Display "SPI Flash to Device succeddful"
But, the access error was not improved.

Do I have any things that I should confirm?

Thanks and Regards,
Tamio

Hi Eric,

I'm having a similar problem as described above when trying to use the Host Interface Tool as well as the Application Customization Tool. I followed the advice above and toggled the "Force Enable" switch so that ResetN is pulled high. This is the failure I'm getting:

I'm using I2C address 0x3F, bitrate of 100 Kbps, and I2C Port 1. Please advise.

Thank you,

T.J.

Eric,

Yes, that is the configuration of my FTDI board. I had it in the configuration in the image below when I received the error.

Hi T.J.,

Can you check in your Device Manager on windows to see what the FTDI shows up as?

You should see USB Serial Converter A-D appear.

Thank you,

Eric

When I look in device manager my FTDI shows up as USB Serial Converter A-D as above and creates 4 COM ports.

Hi Thomas,

It appears from the previous image you sent that the I2C communication failed. Can you try to load a full-flash image onto the TPS65981 through SPI? You can do this by clicking on SPI FW Update.

Thank you,
Eric

I can try. Which image should I load and where can I download these images?

Eric,

I created an image with the customization tool following your instructions. I then tried to program it using the Host Interface Tool's SPI FW Update and got the following error:

Hi Tamio,

Do I have to have version 2.8.2 of the driver in order for the COM ports to work properly? I have version 2.12.24 of the FTDI driver.

I allowed the TPS6598x Application Customization Tool and TPS6598x Host Interface Tool update my FTDI driver when I installed them. I installed the Application tool first and the Host Interface tool second.

Thanks,

T.J.

Hello Tamio,

In some cases we have seen driver conflicts with the FTDI CDM driver package.  FTDI website recommends uninstalling all previous FTDI driver installs before installing a new version of the driver.  They provide a de-installation tool for this purpose:

The command-line version of this de-installer will be run if the "Remove Previous FTDI USB Drivers" checkbox is selected in the installer:

We have also seen that different versions of the FTDI driver work on some version of Windows but not others.  Older Windows installations seem to respond best to version 2_08_24:

http://www.ftdichip.com/Drivers/CDM/CDM20824_Setup.zip

Whereas newer versions may respond better to the latest version:

http://www.ftdichip.com/Drivers/CDM/CDM21226_Setup.zip

Other users have also reported success with 2_12_16 and 2_12_24 where others failed:

http://www.ftdichip.com/Drivers/CDM/CDM21216_Setup.zip

http://www.ftdichip.com/Drivers/CDM/CDM21224_Setup.zip

More informatoin is also available with the FTDI Installation Guide:

http://www.ftdichip.com/Support/Documents/InstallGuides.htm

 

Hi, Steve,

TPS65988 GUi Tool  was solved on FTDI driver issuu of GUI tool because all FTDI driver is removed at once, and then FTDI driver is installed.

Is this function removing FTDI driver implemented in other PD controller deivce?

If it is not implemented yet, I think that the application note for solving FTDI driver issue should be released sooner.

Tamio

Steve,

I am running Windows 7. I tried all of the driver version above, uninstalling whichever driver version was currently installed before using a different version. None of the versions worked for me, in each case I was not able to configure the device over I2C or with the SPI FW Update.

I received an Aardvark programmer yesterday. I have also tried using this to communicate over SPI with no success after connecting it with an octopus cable. I received the following error when trying to use the Aardvark.

Steve,

Following the instructions above I was able to get the SPI flash programmed with the Aardvark.

I still cannot communicate over I2C with the TPS65981, but now that I'm able to program the part over SPI with the Aardvark I don't need that functionality anymore.

Thanks!
T.J.

Was this fully resolved?  I'm getting the same errors.  From what I can tell, the TPS65981 tool is not finding the i2c COM port.  If I snoop the i2c bus with a Bus Pirate and poke values in through a terminal emulator for the i2c COM port, I see i2c activity.  However, the TPS65981 tool generates no activity.

I know the FT4232H is alive - if I wire the ports 3 and 4 UARTS together, I can pass data.  Port 2 is not configured as a UART, which I know because wiring it to port 3 produces no similar pass-through.  

This seems like entirely a tool issue with finding the serial ports.  Are there specific COM ports that must be assigned to the SPI and i2c VCP's?