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.

MSP-EXP430G2: Trouble Writing Block, Target Failed to Write

Genius 15029 points

Part Number: MSP-EXP430G2

Hello Team,

I have a customer using MSP-EXP430G2 development kit. Below is the summary of his report:

"Error:

MSP430: Trouble Writing Memory Block at 0xffe4 on Page 0 of Length 0x4: Could not write device memory
MSP430: File Loader: Verification failed: Target failed to write 0xFFE4

I was thinking about the fault with the chips and try another new one and it gives me the same error. 
Is there any suggestion to debug this error?"

I tried helping him by giving all the related links posted here in E2E that may solved his problem but still no avail. Also, advised him to post on this forum but unable since he is using an organization email account. For the meantime, I will me relaying his follow-up post on his behalf to our E2E.

Thanks for the support.

Regards,

Archie A.

  • You can ask him for binary hex / txt file that cause verification error, replace FFFEh address contest with FFFFh value and test flashing on your side.

  • Hi Zrno. Thanks for the response. He tried but this is his reply:

    I did not catup your meaning: 
    The fellowing hex file is in text file
    @c000
    21 83 B2 40 80 5A 20 01 D2 D3 22 00 D2 E3 21 00
    B1 40 10 27 00 00 81 93 00 00 F8 27 91 83 00 00
    81 93 00 00 F3 27 FA 3F 31 40 00 04 B0 12 4A C0
    0C 43 B0 12 00 C0 1C 43 B0 12 44 C0 32 D0 10 00
    FD 3F 03 43 03 43 FF 3F 03 43 1C 43 30 41
    @ffde
    FF FF 3C C0
    @ffe4
    3C C0 3C C0
    @ffea
    3C C0 3C C0 3C C0 3C C0 3C C0 3C C0 3C C0 3C C0
    3C C0 3C C0 28 C0
    q
      The fellowing hex file is in hex file  
    :20C000002183B240805A2001D2D32200D2E32100B1401027000081930000F8279183000083
    :20C0200081930000F327FA3F31400004B0124AC00C43B01200C01C43B01244C032D0100050
    :0EC04000FD3F03430343FF3F03431C433041D6
    :02FFDE00FFFF23
    :02FFE0003CC023
    :02FFE4003CC01F
    :02FFE6003CC01D
    :02FFEA003CC019
    :02FFEC003CC017
    :02FFEE003CC015
    :02FFF0003CC013
    :02FFF2003CC011
    :02FFF4003CC00F
    :02FFF6003CC00D
    :02FFF8003CC00B
    :02FFFA003CC009
    :02FFFC003CC007
    :02FFFE0028C019
    :00000001FF
    Could you let me know how do I deal with that? 
    Meanwhile, how do I program the modified hex to emulation board.
     

    Looking forward to hear reply from experts.

    Thanks.

  • Just to check that txt file is OK, try to upload it to G2 LP, you (Archie), not costumer. For example with MSP-Flasher, and than (if it is working OK), send MSP-Flasher command line with arguments to costumer to check it.
    @c000
    21 83 B2 40 80 5A 20 01 D2 D3 22 00 D2 E3 21 00
    B1 40 10 27 00 00 81 93 00 00 F8 27 91 83 00 00
    81 93 00 00 F3 27 FA 3F 31 40 00 04 B0 12 4A C0
    0C 43 B0 12 00 C0 1C 43 B0 12 44 C0 32 D0 10 00
    FD 3F 03 43 03 43 FF 3F 03 43 1C 43 30 41
    @ffde
    FF FF 3C C0
    @ffe4
    3C C0 3C C0
    @ffea
    3C C0 3C C0 3C C0 3C C0 3C C0 3C C0 3C C0 3C C0
    3C C0 3C C0 FF FF
    q
  • Thanks for your reply, Zrno. Unfortunately here in our engagement we don't have access to install applications involving IDEs. We are just relying to some expert here in the forum.

  • Archie,

    Are you using CCS to flash the board?  Do you see this same error if you try to load a different project?  Code examples can be found below that can be tested.

    https://dev.ti.com/tirex/explore/node?node=AJ5AfV20axh2lCwpykHEjA__IOGqZri__LATEST&search=G2 

  • Hello Eddie,

    Thank you for your response. Up until now, we're still waiting for the update from the customer.

    Will let you know once I receive feedback on this.

    Thanks for supporting.

    Regards,

    Archie A.

**Attention** This is a public forum