topic Re: Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory. in CodeWarrior Development Tools

Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory.

Wangerxi — Thu, 21 Oct 2021 08:30:52 GMT

I use SWD download software, it doesn't work. Information as below:

Failed to resume target process.
ARM GDI Protocol Adapter : An error occurred while trying to write memory. The Debugger can not write memory.

Looking forward your reply, thanks in advance.

Re: Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory.

Wangerxi — Thu, 21 Oct 2021 08:44:20 GMT

/*Here is my code*/

#define SEC_SECTOR 0xFE00

uint8_t *pData8Bytes = 0;
uint8_t dataSend[4] = {0x01,0x02,0x03,0x04};

FLASH_EraseSector(SEC_SECTOR);
FLASH_Program(SEC_SECTOR,dataSend,4);
pData8Bytes = ((uint8_t *)SEC_SECTOR);

After download the code ,the next time i can't download and print "Failed to resume target process.
ARM GDI Protocol Adapter : An error occurred while trying to write memory. The Debugger can not write memory."

Re: Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory.

diego_charles — Sat, 23 Oct 2021 23:42:47 GMT

Hi @Wangerxi

There is a check-list , that our colleague Erich Styger made, time ago : Debugging Failure: Check List and Hints I just recommend it as it is very handy . Regarding your problem, like point 19 of the post, verify if you have not bricked the MCU, and try to perform a mass erase on the MCU.

As I understand, you are now facing that problem, after you have tried to write a specific sector of the MCU from the application.

Other recommendation is to try to use an aligned address for #define SEC_SECTOR, considering that there first sector of the flash begins at 0x0000_0000 and that there is a sector every 512 bytes.

All the best,

Diego.

Re: Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory.

Wangerxi — Mon, 25 Oct 2021 01:59:18 GMT

Hi Diego,

Thank you for your reply, my issue seems different, I might erased the first sector of the flash begins at 0x0000_0000, and will the chip be bricked?

Best

Erxi

Re: Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory.

diego_charles — Mon, 25 Oct 2021 02:28:49 GMT

Hi @Wangerxi

Thank you for letting me know.

In that case , yes it could be the case that you have bricked the MCU.

At the first sector of the flash there is field at 0x400 , containing security settings. Specially at 0x40C offset there is a byte called FSEC, normally it has to be written with ones ; it contains critical fields controlling Security and mass erase enable that if they are written with zeroes, they will protect the MCU.

You did not necesarilly bricked for ever the MCU. If you only enabled security you could disable it back, regaining debug access. But if you also disabled the Mass erase, you will not be able to recover the MCU with the SWD/ JTAG or any external interface.

Re: Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory.

Wangerxi — Mon, 25 Oct 2021 02:40:23 GMT

Thanks for your declare, I got it.

Re: Use codewarrior11 MCU:KEA64 when debug a problem occurs:The Debugger can not write memory.

diego_charles — Mon, 25 Oct 2021 21:49:06 GMT

Hi @Wangerxi

Thank you for your reply,

Let me know if you still have related questions or problems.

Diego.