MSP430F5342: Verify fail with MSP Flasher

And MSP Flasher command line is?

Have you tried using uniflash? 

Please post the MSP flasher command file. 

Regards,

Evan

Sorry, command line : C:\ti\MSPFlasher_1.3.20\MSP430Flasher.exe -s -w "test.txt" -e ERASE_MAIN -v -z [RESET, VCC=2100]

I also try without '-s', I haven't probe update request and I have the same result

I haven't tried UNIFLASH but why would it be better than MSPFlasher?

Is "test.txt" only in main flash? What if you split one MSP Flasher call in two ...

C:\ti\MSPFlasher_1.3.20\MSP430Flasher.exe -e ERASE_MAIN  -w "test.txt" -z [RESET, VCC=2100]

C:\ti\MSPFlasher_1.3.20\MSP430Flasher.exe -v "test.txt" -z [RESET, VCC=2100]

Yes I want to update only main flash.

Same result if I try split command

But it works if I remove the binary code (in the test.txt file) that writes to the @1800 and @1980 memory addresses.
Is it normal that we can't check a code written at these addresses?

For erasing info memory (1800h - 19FFh) must be used "-e ERASE_ALL"

ok, but the check does not indicate a bad comparison. The error code is "Could not terminate EEM polling thread", so I understand that the probe fails during the check.
Or should I consider the error code as a wrong comparison?

When I erase the binary code that is written at @1800 and @1980 (segment A and D of the information memory). The verification is OK but I did not erase all the memory between the two tests.

Before writing to info segment(s) with MSP Flasher, info memory must be erased. Verify will check binary file against device memory in same address space. In your example verify is failing because binary file contest is not 100% same as device memory. MSP Flasher verify error report looks exactly like yours, nothing to do with "Could not terminate EEM polling thread". If probe fails during check, it will fail in both cases, with and without verify error.

I always split the program and verify command. I changed the erase command to ERASE_ALL in the programming request and I get the same result.

If I erase the binary code that writes to the Info SegmentA memory, the D segment is retained, the verification is OK. Do you know why the probe verification fails if I write to SegmentA?

I try with ERASE_SEGMENT and ERASE_TOTAL option but I have the same result