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.

MSP430: Trouble Writing Memory Block at 0x8000 on Page 0 of Length 0x30: Could not erase device memory

Part Number: MSP430F5510
Other Parts Discussed in Thread: UNIFLASH

Hi,

Recently, I was working on MSP430F5510  MCU by using MSP FET flash emulation tool.

At the start of using CCSv6, I can normally debug my device, but several times later, I found it cannot erase memory anymore.

The image file is test.out

For solve this issue, I have tried uniFlash to load image, but still failed like below:

[10/14/2022, 1:23:57 PM] [ERROR] MSP430: Trouble Writing Memory Block at 0x8000 on Page 0 of Length 0x30: Could not erase device memory
[10/14/2022, 1:23:57 PM] [ERROR] MSP430: File Loader: Verification failed: Target failed to write 0x08000

My start and end address limits for erase as follows:

The memory can read out normally.

So I wonder if the flash memory has been locked up, I used MSP430Flasher to unlock memory and erase it.

The commends and feedback is like below:

C:\ti\MSPFlasher_1.3.20>MSP430Flasher.exe -u

C:\ti\MSPFlasher_1.3.20>MSP430Flasher.exe -e ERASE_ALL

From the message shows, the memory is unlock status, but still erasing failed. 

So could you help to advise for this issue ?

What's the possible reason and how can I do to resolve it ?

  • 1. Can you let Uniflash do Mass erase? And check whether it is successful.

    2. Read the TLV data and check whether it is right.

    3. Download a blink LED or an example code into the device to see whether it is successful.

  • Hi Eason,

    First of all, thanks for your reply,

    For the first advice, it failed, the print log shows below:

    [10/17/2022, 9:26:01 AM] [ERROR] MSP430: Error erasing Flash memory.
    [10/17/2022, 9:26:35 AM] [ERROR] MSP430: Error: Could not erase device memory

    For the second, the memory value is showed as follows, it seems different with datasheet.

    For the last advice, the situation is the same as before, nothing changed.

    Thanks

    Kevin

  • HI Eason,

    This issue has been resolved, the problem happened in poor wire contact.

    Thanks for your advice again.

    Kevin

**Attention** This is a public forum