• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 50 subscribers
  • Views 184 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: LM51772 GUI recommends me to update firmware to 4.1.0.1 but doesn't seem to do anything and unable to find SDK file online

Alexandre Steffen
Prodigy 10 points
Part Number: USB2ANY
Other Parts Discussed in Thread: LM51772EVM-HP, , LM51772

Tool/software:

I'm pissed atm, I ordered the USB2ANY with my LM51772EVM-HP so I can directly test my use case without designing a prototype.
I tried to connect everything but the USB2ANY needs a firmware update to 4.1.0.1 and the GUI software (website and desktop software) doesn't seem to do anything or it's spiting errors when I accept the update even with or without holding the BSL button (i tried alot of deferent ways).
I wanted to go the manual update route but I can't find any update files on the website/product page etc.
I tried a lot of options and I'm not rewriting everything.
I just want to have a working USB2ANY device communicating to my LM51772EVM-HP so I can finally get my planned work done.

I know it's a evaluation module/board but putting a lot of money into these devices to in the end not beiing able to make it work (almost) first try or having a simple flashing tool with easily accessible files to update the tool with is a bit of a joke.

  • 0
    Prodigy 110 points

    I was wondering about buying a USB2ANY for this same demo board so I'd like a response when you can.  Also I was hoping to get the Altium schematic and PCB files if they are available.  Thank you.

  • 0
    TI__Genius 14885 points

    Hi Alex,

    Sorry for the inconvenience. I re-assigned this thread to USB2ANY support team.

    Best Regards,

    Feng

  • 0 in reply to Feng Ji
    TI__Genius 14930 points

    The gui does use a simple command line firmware update utility. The output shown red in your picture is the output from that command line utility. It seems to indicate that the update process failed half way through. 

    You could try running it from command line to see if there is some sort of unusual interaction to eliminate a few layers of software. 

    The command line utility is located in: C:\Users\YourWindowsUserID\guicomposer\runtime\gcruntime.v12\runtime\deskdb\content\TICloudAgent\win\ccs_base\bsl

    The executable is inside win32 directory. It accepts a single command line argument, which is a script to use for firmware update. USB2ANY is specifically using a pre-package script and additional files located in 5xx_usb directory. The only tricky part is that included script.txt has a token that is replaced on line #9 programmatically rather than actual name of txt file. I have attached script.txt that has that token replaced with USB2ANY_2_8_2_0.txt. Please put it in 

    C:\Users\YourWindowsUserID\guicomposer\runtime\gcruntime.v12\runtime\deskdb\content\TICloudAgent\win\ccs_base\bsl\5xx_usb\ directory. 

    It is not the version that GUI is looking for, however, I think it would be good to try and program a firmware version with known version. I do not work with LM51772 device and do not have access to one, hence using something that I am familiar with would be my suggestion. 

    Once we prove that process works, we can adjust things and try to update with firmware version that GUI is expecting. 

    Thus if you are ok, you could open command window in C:\Users\YourWindowsUserID\guicomposer\runtime\gcruntime.v12\runtime\deskdb\content\TICloudAgent\win\ccs_base\bsl\win32

    and run 

    bsl-scripter.exe "C:\Users\YourWindowsUserID\guicomposer\runtime\gcruntime.v12\runtime\deskdb\content\TICloudAgent\win\ccs_base\bsl\5xx_usb\script.txt"

    If this works, then we can update script.txt and specify the firmware version that GUI is expecting. 

    If this does not work, then it might be bad HW or maybe some other HW or SW issue that is interfering with data transfer. 

    Martin

    script.txt 
    MODE 5xx USB
RX_PASSWORD pass32_wrong.txt
RX_PASSWORD pass32_default.txt
RX_DATA_BLOCK_FAST RAM_BSL_USB.txt
SET_PC 0x2504
DELAY 3000
MODE 5xx USB
RX_PASSWORD pass32_default.txt
RX_DATA_BLOCK USB2ANY_2_8_2_0.txt
SET_PC 0x4400