MSP-FET: About error code of MSP-FET

Part Number: MSP-FET
Other Parts Discussed in Thread: MSP430F149, , UNIFLASH

Tool/software:

When writing to the target microcontroller MSP430F149 using MSP-FET with MSP430Flasher.exe,
the result is as follows:


----
PS C:\ti\MSPFlasher_1.3.20> .\MSP430Flasher -n MSP430F149 -w C:\work\C6572301V0100.hex -v
-----/|-------------------------------------------------------------------- *
/ |__ *
/_ / MSP Flasher v1.3.20 *
| / *
-----|/-------------------------------------------------------------------- *
*
Evaluating triggers...done
Checking for available FET debuggers:
Found USB FET @ COM5 <- Selected
Initializing interface @ COM5...done
Checking firmware compatibility:
FET firmware is up to date.
Reading FW version...done
Setting VCC to 3000 mV...done
Accessing device...done
Reading device information...done
Loading file into device...done
Verifying memory (C:\work\C6572301V0100.hex)...
# Exit: 10
# ERROR: Could not reset device
Powering down...done
Disconnecting from device...done
*
----------------------------------------------------------------------------
Driver : closed (No error)
----------------------------------------------------------------------------
*/
PS C:\ti\MSPFlasher_1.3.20>
----

Question 1
Has the writing process succeeded or failed?


Question 2
The output shows "Exit: 10" and "ERROR: Could not reset device".
The process exit code is also 10. However, in the slau654e.pdf document,
table 9 "Error Codes" shows that Error Code 10 means "Could not set device Vcc",
which is different. Are the Exit value and Error code separate values?
If they are separate, where can I find a list of Exit values?

  • Hello Kei,

    Can you try to download using UniFlash because I think there maybe no one can support the issue of the MSP430 Flasher.exe currently. 

    Best Regards,

    Janz Bai

  • In FET firmware sources, error handling is not perfectly clear. Only way to be 100% sure (what is going on in your case) is to debug FET itself (with another JTAG master) together with msp430.dll. More or less, mission impossible.

    MSP Flasher only using msp430.dll functions, same as UniFlash.

**Attention** This is a public forum