MSP430G2231: MSP Flasher Exit:60 verification failled

I don't see erase in MSPFlasher command line

Hi,

I have tried this, but this doesn't give a different result. Also tried to first erase_all, tried also an erase total. But always the same result. 

If I read the datasheet correct erase_all is the standard that the flasher uses so I would guess I don't need to add this setting. 

Kind regards,

Dieter

Can you try it with firmware.txt (TI txt format), and if it fail attach firmware.txt file here.

You don't need to use "-n" because target device should be auto detected / recognized automatically.

Hi,

This gives the same result. Attached is the hex file. 

Kind regards,

Dieter

I just changed last 2 bytes in txt file to 0xFF because I don't want to run it, and there is no problem with flashing using 5529 LP as master and G2553 as target device...

D:\msp>msp430flasher -e ERASE_ALL -w firmware.txt -v -z[VCC]
* -----/|-------------------------------------------------------------------- *
*     / |__                                                                   *
*    /_   /   MSP Flasher v1.3.20                                             *
*      | /                                                                    *
* -----|/-------------------------------------------------------------------- *
*
* Evaluating triggers...done
* Checking for available FET debuggers:
* Found USB FET @ COM7 <- Selected
* Initializing interface @ COM7...done
* Checking firmware compatibility:
* FET firmware is up to date.
* Reading FW version...
* Debugger does not support target voltages other than 3000 mV!
* Setting VCC to 3000 mV...done
* Accessing device...done
* Reading device information...done
* Loading file into device...done
* Verifying memory (firmware.txt)...done
*
* ----------------------------------------------------------------------------
* Arguments : -e ERASE_ALL -w firmware.txt -v -z[VCC]
* ----------------------------------------------------------------------------
* Driver : loaded
* Dll Version : 31501001
* FwVersion : 31200000
* Interface : TIUSB
* HwVersion : E 3.0 (eZ-FET lite)
* JTAG Mode : AUTO
* Device : MSP430G2xx3
* EEM : Level 1, ClockCntrl 1
* Erase Mode : ERASE_ALL
* Prog.File : firmware.txt
* Verified : TRUE
* BSL Unlock : FALSE
* InfoA Access: FALSE
* VCC ON : 3000 mV
* ----------------------------------------------------------------------------
* Starting target code execution...done
* Disconnecting from device...done
*
* ----------------------------------------------------------------------------
* Driver : closed (No error)
* ----------------------------------------------------------------------------
*
* 6241 msec

D:\msp>

EDIT: I don't know what is default interface speed selected in CCS, and don't remember if default MSP430Flasher is low speed (it should be medium), so you can try it with "-j slow"

Hi,

Still receive the same result. I have tried this on 5 different boards. Still the same result. 

Kind regards,

Dieter

You noted that with CCS firmware update is working fine, but I am not sure if in CCS verify is enabled or not.

Standalone mass erase in your case is working fine, so I guess that everything is OK related to FET-target connection. Guess that power supply is OK.

You can try to divide MSP430Flasher action in 3 separated steps to see if only verify (last step) is failing.

1. -e ERASE_ALL

2. -w firmware.txt

3. -v firmware.txt

AFAIK, with msp430.dll verify is done by PSA CRC calculation. After flashing and reported verify error you can export target device flash content to ti txt file and compare it with original file with text editor manually, to see if there any difference.