Other Parts Discussed in Thread: UNIFLASH, , MSP430F6736, MSP-FET, MSP430F5438, MSP430-FLASHER, MSP-FLASHER, TEST2
I am trying to make a simple system to program boards from the command line so UniFlash is not needed. I am running version 4.2.0.1490 of UniFlash. I create a "Standalone Command Line" package from within UniFlash. I take the uniflash_windows_64.zip and unzip it into a folder, run "one_time_setup.bat" then "dslite.bat", and DSLite (version 7.2.0.2096) always gives me the following error:
Executing Startup Scripts: MSP430
Connecting...
error: MSP430: Error connecting to the target: Unknown device
Failed: Operation was aborted
I turned on logging in the dslite.bat batch file (-g blinker.log) and found the following in blinker.log:
0x000017EC 1201 3 MSP430 MSP C: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 )
0x000017EC 6084 3 MSP430 MSP R: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 ) = -1
0x000017EC 6084 3 MSP430 MSP C: MSP430_Error_Number()
0x000017EC 6084 3 MSP430 MSP R: MSP430_Error_Number() = 5
0x000017EC 6084 3 MSP430 MSP C: MSP430_Error_String( 5 )
0x000017EC 6084 3 MSP430 MSP R: MSP430_Error_String( 5 ) = Unknown device
0x000017EC 6084 3 MSP430 GTI R: GTI_CONNECT( 0x02666268 ) = 0xFFFFFFFF
0x000017EC 6084 3 PERF I: GTI_CONNECT finished: 4.884457s wall, 0.000000s user + 0.000000s system = 0.000000s CPU (n/a%)
I can get the device to program from UniFlash itself, but I want to use the command line tool for production. From UniFlash, I get the following in the log (from ds.log):
0x000016A4 344603 3 MSP430 MSP C: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 )
0x000016A4 345270 3 MSP430 MSP R: MSP430_OpenDevice( MSP430F5438A, , 0, 0x0, 0 ) = 0
Why is DSLite failing and UniFlash succeeding? Is there a way to get the internal function "MSP430_OpenDevice()" to succeed from the command line through the DSLite tool? Please let me know.
Thank you,
Mike