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.

USB2ANY (with LM2571 EVM) unable to update/connect

Other Parts Discussed in Thread: CODELOADER, USB2ANY, LMX2571

I recently got a LMX2571 EVM which came with a USB2ANY module. I installed Codeloader 4 as mentioned in the user manual http://www.ti.com/lit/ug/snau176a/snau176a.pdf

When I connect the USB2ANY with codeloader 4 running, I get an error that a USB2ANY firmware update is required

Windows finds a HID driver for USB2ANY in default mode but does not identify it in BSL mode. Attempting to update the driver of the unknown device by pointing to the Program Files(x86)/Texas Instruments/Codeloader 4/ directory (with subdirectory search on) does not install any of the packaged drivers (if any) 

Things I've already tried to solve the issue:

1. Rebooting the Windows 7 system

2. Unplugging and reconnecting USB2ANY on 4 different USB ports

3. Using a different Windows machine

4. Trying to put USB2ANY into BSL mode multiple times

5. Using the manual update application in Program Files(x86)/Texas Instruments/Codeloader 4/USB2ANY Firmware Loader

6. Running Codeloader & Firmware Loader with administrative privileges

I've also read through and tried any solutions mentioned on the following forum posts:

https://e2e.ti.com/support/clocks/f/48/t/414136

https://e2e.ti.com/support/applications/motor_drivers/f/38/t/443058

How do I solve this?

Alternatively for future work, do you have a simple command line tool or API (for *NIX systems without mono/emulation/VMs) which does the same operation in a more verbose manner?

  • Adwait,

    You are already at the right place. When there is a new Firmware released, you will get this pop up. Just press OK and you should go through the instructions on how to upgrade. see attached slides that goes through that too.USB2ANY firmware_OLD.pptx

  • After a lot of tweaking around, I finally managed to get CodeLoader's firmware updater to work.

    The solution was NOT to install Codeloader in the default location in Program Files (Change it so something else like C:\Codeloader).
     Installed elsewhere, the update application works fine.


    I would still love to have a *NIX command line tool for this though.

  • Adwait,

    Thank you for your feedback regarding CodeLoader.  I am not a big fan of installing things to the program files directory because when you do, windows actually uses another directory called the "Virtual Store".   This has caused confusion and issues with CodeLoader and we do mention that you might not want to install it to the program files directory in the CodeLoader instructions.

     

    Regards,

    Dean