Hardware failure after operations with FRDM-64F program memory flash

Showing results for 
Search instead for 
Did you mean: 

Hardware failure after operations with FRDM-64F program memory flash

Contributor I


I am performing read and write operations in the flash of my FRDM-64F. Using the fsl_flash KSDK 1.2.

I created the memory areas:


In execution of the erase flash operation. The FRDM-64F does not work anymore. Lost communication and does not accept the writing of new hardware:


The RESET LED is slightly access (apparently oscillating) and when you press the reset button it lights normally:

2015-12-11 18.03.12.jpg

2015-12-11 18.03.59.jpg

The event happened during debbug program in this passage:

result = flash_app_EraseSector (flash_app_destAdrss(1,&flash1_InitConfigAlarme),1,&flash1_InitConfigAlarme);

The function is:

uint32_t flash_app_EraseSector (uint32_t destAdrss, unsigned char qtdeSetor, FLASH_SSD_CONFIG *FlashBlk){

uint32_t result;

if(!qtdeSetor) qtdeSetor = 1; // Se for 0 ou não existir, assume 1.


//result = FlashEraseSector(&flash1_InitConfig0, destAdrss, qtdeSetor * FTFx_PSECTOR_SIZE, g_FlashLaunchCommand);

result = FlashEraseSector(FlashBlk, destAdrss, qtdeSetor * FTFx_PSECTOR_SIZE, g_FlashLaunchCommand);


return result;


What happened?

How to get back to normal?

Thank you and I hope me someone help me.

Juandres M. Lazaro

0 Kudos
2 Replies

NXP TechSupport
NXP TechSupport

Hello Juandres M. Lazaro ,

Now please test one simple project , check whether it can debug well .

If it also not not download and debug , please update the bootloader of your board refer to the

"FRDM-K64F Freedom Development Platform -Quick Start Guide.pdf" .

I see you use the OpenOCD debug mode,  you need drag and past  the drive again to the bootloader;

or you can also use the segger jlink debug mode , you need  drag and past the "JLink_OpenSDA_V2.bin" to the bootloader .

Hope it helps

Note: If this post answers your question, please click the Correct Answer button. Thank you!

Have a great day,
Alice Yang

Specialist V


I don't know what went wrong bt it is possible to leave the chip in a state where it resets when the debugger is trying to take command of it which results in difficulties.

Usually this can be solved by configuring the debugger to immediately erase the chip on connect. In the Flash configuration's Debugger setup selet the "Mass erase on connect" option:




Kinetis: http://www.utasker.com/kinetis.html

K64: http://www.utasker.com/kinetis/FRDM-K64F.html / http://www.utasker.com/kinetis/TWR-K64F120M.html / http://www.utasker.com/kinetis/TWR-K65F180M.html

Serial Bootloader for K64 (Ethernet, USB, MSD, KBOOT, AN2295, SREC, SD-card, Memory Stick, Virtual COM SREC): http://www.utasker.com/forum/index.php?topic=1873.msg6796#msg6796 / http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.PDF

For the complete "out-of-the-box" Kinetis experience and faster time to market

0 Kudos