Part Number: *****>
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.
Hi Kenley,
For .exe, you can generate it by using GUI_EXE_Update.bat.
And no it cannot be used on the command line.
For uniflash, updating via BSL is a new function, so there is no document on it now. I will check with team about this requirement.
HI Zhao,
Thank you for your support.
I have tried to generate using the .bat file but it is said as following.
Python the specified path is not found. 'Pip' is an internal or external command, It is not recognized as an operable program or batch file. 'Pyinstaller' is an internal command or an external command, It is not recognized as an operable program or batch file. The specified path cannot be found. Press any key to continue...
But after pressing any keys, the window is closed down.
Any suggestion ?
Best regards,
Kenley
Please try this one.
https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/908/MSPM0_5F00_BSL_5F00_GUI.exe
Hi Zhao,
It seems like working now.
Thank you.
May i know where do you get that .exe from ?
Best regards,
Kenley
.bat file need to work with python environment. And I get .exe from my team, which is same as what .bat generates.
Noted. Thank you.
Regarding uniflash, looking forward to your feedback after the confirmation.
Hi Zhao,
Regarding that it can not be used on the command line, customer has additional question.
In circuit board factories, we believe that automation is necessary, such as automatically writing firmware from a function tester to an MCU.
I'm sure other users are doing the same, but how do you process batches (command line processing)?
Regards,
Kenley
For BSL, there is no command line to implement it yet. But the flow to implement BSL host is described in ti.com/lit/an/slaae88c/slaae88c.pdf?ts=1747190824745&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FMSPM0L1306%253FkeyMatch%253DMSPM0L1306%2526tisearch%253Dsearch-everything%2526usecase%253DGPN.
Hi Zhao,
Okay thank you.
Btw back to the bsl.exe, customer has tried it but the following error came out.
====
Find MSP COM port:COM20
Configure UART: 9600 baudrate, 8 data bits (LSB first), no parity, and 1 stop bit.
Error: No response!
===
They would like to know how to deal with it.
As described in Table 3-5. Standalone Signal Connection in Slaae88c.pdf,
the wire is connected, but BSL_invoke does not appear to be asserted when checked with oscilloscope.
Best regards,
Kenley
This is a conversion board that comes with the purchase of the XDS110 debug probe.
So you are using a standalone xds110 or on-board xds110? Please check the signal connection again.
Using Standalone XDS110 , we have checked the signal connection and it is the same with the table.
We tested it before and it should work. Could you use xds110 on launchpad and test it again?
Then the GUI should be good. Could you try another standalone xds110? Or try using AUX port on it?
They tried Uniflash and was able to write through the Debug connector (SWD interface) of the XDS110 Debug Probe, but it still did not work through the AUX connector (UART to BSL).
I checked with Gary and the root cause is the wrong selection on the GUI.
If there is no more question, I will close this thread.