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.

TPS65400EVM-678: USB2ANY - PI Commander driver issue

Part Number: TPS65400EVM-678
Other Parts Discussed in Thread: USB2ANY, TPS65400

It's been a year since I've run PI-Commander Version 0.8.5. 

Windows 10 Home

64 bit

V1809

I'm getting

"Incompatible FTDI device drivers have been detected. To resolve this issue, please exit the program and install compatible drivers which are bundled withthis application. The driver installer is accessible from the "PI-Commander-0.8.5" system menu. Acknowledge"

I've tried uninstalling and then re-installing the drivers already present on the machine that were working before. This did not work.

I followed the link in the TI folder in the windows start menu to "Download USB Drivers" which took me to "https://www.totalphase.com/products/usb-drivers-windows/" . Uninstallled the drivers using the "Uninstall Drivers" under the TI folder in the start menu. Then I installed the rivers from totalphase. This also did not work.

Where is the current version of PI Commander and associated Drivers?

  • Hi, Mark

    The latest PI Commander is at the bottom of below webpage, it is 0.8.5 version, it looks you have the right version.

    http://www.ti.com/product/TPS65400/toolssoftware

    I think it might be a common communication issue.

    Please try the solution in below post: 

    Update the USB2ANY firmware to lower versions(USB2ANY_1_19_0_0.txt)

    https://e2e.ti.com/support/power-management/f/196/p/718433/2653556?tisearch=e2e-sitesearch&keymatch=690036#2653556


    http://www.ti.com/tool/USB2ANY?keyMatch=USB2ANY&tisearch=Search-EN-everything

     

  • I have a faint memory of the TI Commander not working with the most recent version of USB2ANY firmware when applying it to the 65400. 

  • Hi, Sir

    This communication problem is strange, not all of customers have this issue when using same Windows system.
    so far, the work around is to Update the USB2ANY firmware to lower versions.

  • Yes. How do you do this though?

    When I use the USB2ANY Explorer.exe or USB2ANY Firmware Loader.exe the alternate firmware version does not appear in the dropdown list. I placed the alternate firmware file in the C:\Program Files (x86)\Texas Instruments\USB2ANY Explorer\Bin\Firmware and have tried placing it in "C:\Users\mjn\Documents\tmp"

    When I specify the filename with a path in the dropdown box I get the message "ready to update firmware to version 255.255.255.255" . I've also tried specifying the filename without a path and I've tried specifying the file without the .txt file extension. 

  • Hi, Mark

    You can try to place file(USB2ANY_1_19_0_0.txt) to below directory, then restart computer to check if it is showed in dropdown list. (USB2ANY Firmware Loader.exe)

  • there is a difference in the directory tree from what I have installed and what you have listed. 

    I notice your installation is for the USB2Any SDK (software development kit). This is part of the issue. I'm guessing your developer only tests the software on a development machine. 

    The revision number I have for both the non-SDK installation and the SDK installation are the same at 2.8.2.0 although I suspect they are a different code base.

    I managed to get the dropdown populated with the downgraded firmware image. 

    1. Uninstall any previous versions of USB2ANY Explorer software

    2. Install the full SDK version of the USB2ANY software. Unfortunately I cant locate where I found the SDK installation. Please provide the link to it.

    3. Place the USB2ANY_1_19_0_0.txt file in the firmware folder

    4. Run the USB2ANY Firmware Loader.exe (do not use the USB2ANY Explorer.exe and the advanced button within it. This doesn't work)

    5. For me the USB2ANY_1_19_0_0.txt then showed up in the dropdown list. (Note that although text can be entered in the dropdown list, specifying the file to use does not work)

     

    Please don't just mark this issue as resolved and move on to the next thing. This confusing installation of firmware and programming tools has existed for years now. Presently the toolchain needs to be fixed so that the latest version of USB2ANY firmware and the latest version of PI commander works with the 25400 power controller IC. What you have now is an unpublished workaround whose steps are not clearly defined. At the very least, clearly define the workaround!

     

  •  

    Hi, Mark

    1. I am the hardware engineer, I don't know the difference about non-SDK and SDK version.

    2. The default SDK installation directory in my computer is C:\Program Files (x86)\TI USB2ANY SDK\

    I take a summary for workaround, see the attached.

    You should place the USB2ANY_1_19_0_0.txt to Firmware directory of TI USB2ANY SDK.

    Please try again.

    TPS65400 GUI Connection Issue Workaround.zip

    3. I thought this issue was fixed, so I marked it resolved, it doesn't matter, once you rely this post, this post will be open again and I will receive the E2E mail.

    4. Actually, TPS65400 GUI was released for many years, the most users didn't have this connection issues, and I cannot duplicate this issue in TI internal, to be honest, I don't know the root cause, so this issue was not resolved yet, and didn't publish the workaround.

  • Hello,

    I'm not sure why you cannot reproduce these issues. I suggest you start with a clean installation of the non SDK version of the tools and a brand new USB2Any hardware device. 

    Use a Firmware version later than "USB2ANY_1_19_0_0.txt " and the . The requirement to use a lower version is not clearly documented.

    Try to load "USB2ANY_1_19_0_0.txt " version of firmware into the USB2ANY device using the non SDK version of the firmware tool and you will not see the "USB2ANY_1_19_0_0.txt " show up in the dropdown list

    Try to load "USB2ANY_1_19_0_0.txt " version of firmware into the USB2ANY device using the non SDK version of the USB2ANY Explorer.exe tool and launch the firmware loading tool through the advanced button and you will not see the "USB2ANY_1_19_0_0.txt " show up in the dropdown list

    I have it working now but it cost me a couple days and required your support team to provide the older version of firmware and a bit of random experimentation. I'm asking you document this in an application note listed on the 65400 part page, the 65400 EVM page, and on the USB2ANY device page. Please don't just leave it to people finding it in this support dialog. 

  • Hi, Mark

    1. I meant I cannot reproduce the "GUI communication issue" in my notebook(windows 10) and my colleague's notebook(Windows 7).

    I don't know where is something wrong in GUI, and since "cannot reproduce", the software team also cannot provide a solution for issue.  

    2. I check again, you are right, "USB2ANY_1_19_0_0.txt" doesn't show up in the dropdown list of non SDK version, I will report this to software team.

    3. Sorry for inconvenience, and thanks for continuing support TI's product.

    But I cannot do this "document this issue in an application note listed on the 65400 part page".

    As I mentioned, the most of users didn't have this GUI communication issue, the GUI works normally in computer, they don't need to downgrade to "USB2ANY_1_19_0_0.txt", so my concern is that if I do this, it would confuse them.

    Sorry for in inconvenience again.

  • Hello,

    I've found gui to not find the 25400 device on 3 different computers if the USB2ANY has firmware other than the "USB2ANY_1_19_0_0.txt". I thought you had confirmed this. Yes?

    I'm finding this to be the case in another support thread that you provided here

    https://e2e.ti.com/support/power-management/f/196/p/718433/2653556?tisearch=e2e-sitesearch&keymatch=690036#2653556

    "I think the problem may be firmware version of USB2ANY. Please use version 1_19_0_0. By some unknown reason, version later than that can't support this EVM. You can take below link as reference, which has similar issue.
    e2e.ti.com/.../690036"

  • Hi, Mark

    No, actually, most of users don't need to downgrade the firmware to "USB2ANY_1_19_0_0.txt".

    I will ask the software team what is the difference between "USB2ANY_1_19_0_0.txt" and "USB2ANY_2_8_2_0", and try to find the root cause.  

    Thanks for your advice.