FRDM K64 flashing Problem

[deepaks]

Hi,

I am using FRDM K64 Board for flashing example programs, From past few days am working on freertos examples, it was working fine. Now am getting below error

Tue Dec 26, 2017 17:55:18: IAR Embedded Workbench 7.80.4 (armproc.dll)
Tue Dec 26, 2017 17:55:18: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\debugger\NXP\Kxx.dmac
Tue Dec 26, 2017 17:55:18: Loaded macro file: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\debugger\NXP\K6x_Trace.dmac
Tue Dec 26, 2017 17:55:18: Loading the CMSIS-DAP driver
Tue Dec 26, 2017 17:55:18: Probe: CMSIS-DAP probe SW module ver 1.12
Tue Dec 26, 2017 17:55:18: Probe: CMSIS-DAP S/N '0240022352ee6e4caf3293f4' mapped to a number 00004.
Tue Dec 26, 2017 17:55:18: EARM v.4.14
Tue Dec 26, 2017 17:55:18: Emulation layer version 4.14
Tue Dec 26, 2017 17:55:18: Notification to core-connect hookup.
Tue Dec 26, 2017 17:55:18: MDM-AP detected
Tue Dec 26, 2017 17:55:18: CPU status FAILED
Tue Dec 26, 2017 17:55:18: MDM-AP detected
Tue Dec 26, 2017 17:55:18: MDM-AP detected
Tue Dec 26, 2017 17:55:18: LowLevelReset(script, delay 200)
Tue Dec 26, 2017 17:55:18: Calling reset script: ResetAndDisableWatchdog
Tue Dec 26, 2017 17:55:18: CMD_INTERPRETER: failed
Tue Dec 26, 2017 17:55:18: C:\Program Files (x86)\IAR Systems\Embedded Workbench 7.5\arm\config\debugger\NXP\Kxx.dmac(28,13): Error: Operation error.  
Tue Dec 26, 2017 17:55:18: Error while calling macro ResetAndDisableWatchdog
Tue Dec 26, 2017 17:55:18: MDM-AP detected
Tue Dec 26, 2017 17:55:19: MDM-AP detected
Tue Dec 26, 2017 17:55:19: MDM-AP detected
Tue Dec 26, 2017 17:55:19: MDM-AP detected
Tue Dec 26, 2017 17:55:20: MDM-AP detected
Tue Dec 26, 2017 17:55:20: MDM-AP detected
Tue Dec 26, 2017 17:55:24: Fatal error: Failed to connect to CPU   Session aborted!
Tue Dec 26, 2017 17:55:25: IAR Embedded Workbench 7.80.4 (armproc.dll)
Tue Dec 26, 2017 17:55:27: Loading the CMSIS-DAP driver

I did not change any configuration in IAR settings. Please Help.

Thanks,

[Robin_Shen]

Hi Deepak,

Please update the P&E Micro v118 firmware application for on board OpenSDA debugger.

And then use the Kinetis_Recovery_Utility halt K64. For more detail, please refer: Bricking and Recovering FRDM-KL25Z Boards: Reset, SWD Clock and Low Power.

Hope that help! Have a nice day.

Best Regards,

Robin

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

[davidsherman]

Hi Deepak and Robin, sorry for hijacking but I've run into similar problems with my FRDM-K64F.  I plugged it into my Windows 10 laptop and managed to corrupt it in fairly short order, then discovered the problems with Windows 10.  I have followed the instructions Robin provided using a Windows 7 computer, but I'm a little confused.  I seem to have updated the bootloader with the Daplink bootloader, because now if I plug it in with the reset button pressed, it shows up as a drive labeled "MAINTENANCE" instead of "BOOTLOADER", and according to the text file it is version 0244.  I downloaded the P&E drivers, and if I install "DEBUG-FRDM-K64F_Pemicrov108a_for_OpenSDA_v2.0.bin", it shows up as a Pemicro OpenSDA debugger under Jungo devices in Device Manager, which allows me to program and debug the K64.  However, it seems that to use it as a mass storage device AND debugger, I need the .SDA file "MSD-DEBUG-FRDM-K64F_Pemicro_v114.SDA".  If I start it in bootloader mode and copy that file into "MAINTENANCE", nothing happens.  If I unplug it and reconnect it normally, I don't get a mass storage device.  Am I missing something?