AnsweredAssumed Answered

how to Unbrick a frdm-k64f

Question asked by Michael Perry on Nov 19, 2018
Latest reply on Nov 20, 2018 by Jing Pan

I am trying to unbrick two frdm-k64f boards.  I looked at the info at mcuoneclipse.com and tried the following:

 

I used CW 10.7 and Processor Expert to make a dummy app for a K20.  All it does is toggle the led that is connected to port D4 fo the K20.  I use a PEMicro multilink to download the app and I can debug, step, etc. just fine. LED works.

 

Then I use "flash file to target" and download 0244_k20dx_bl_0x5000.bin.  I power cycle the board and there are no LED's lit and no USB MSD appears.  The output from the flash operation is:

 

***************

fl::target -lc "LC for Simple Flash"
fl::target -b 0x1fffe000 0x4000
fl::target -v off -l off
cmdwin::fl::device -d "FTFL_PFlash128S1RAM16" -o "32Kx32x1" -a 0x0 0x1ffff
cmdwin::fl::image -f "C:\\Users\\micha\\Downloads\\0244_k20dx_bl_0x5000.bin" -t "Auto Detect" -re on -r 0x0 0x1ffff -oe off
cmdwin::fl::erase image
Beginning Operation ...
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Performing target initialization ...
failed on register write: ETF_FCR
Downloading Flash Device Driver ...
Reading flash ID ...
Erasing Sector 0x00000000 to 0x000003FF
Erasing Sector 0x00000400 to 0x000007FF
Erasing Sector 0x00000800 to 0x00000BFF
Erasing Sector 0x00000C00 to 0x00000FFF
Erasing Sector 0x00001000 to 0x000013FF
Erasing Sector 0x00001400 to 0x000017FF
Erasing Sector 0x00001800 to 0x00001BFF
Erasing Sector 0x00001C00 to 0x00001FFF
Erasing Sector 0x00002000 to 0x000023FF
Erasing Sector 0x00002400 to 0x000027FF
Erasing Sector 0x00002800 to 0x00002BFF
Erasing Sector 0x00002C00 to 0x00002FFF
Erasing Sector 0x00003000 to 0x000033FF
Erasing Sector 0x00003400 to 0x000037FF
Erasing Sector 0x00003800 to 0x00003BFF
Erasing Sector 0x00003C00 to 0x00003FFF
Erasing Sector 0x00004000 to 0x000043FF
Erasing Sector 0x00004400 to 0x000047FF
Erasing Sector 0x00004800 to 0x00004BFF
Erasing Sector 0x00004C00 to 0x00004FFF
Erasing ...
Erase Command Succeeded
cmdwin::fl::write
-------------------------
Using restricted address range 0x00000000 to 0x0001FFFF
Programming file C:\Users\micha\Downloads\0244_k20dx_bl_0x5000.bin
Auto-detection is successful.
File is of type Binary/Raw Format.

Downloading Flash Device Driver ...
Reading flash ID ...
Auto-detection is successful.
File is of type Binary/Raw Format.

Downloading 0x00003310 bytes to be programmed at 0x00000000
Executing program ....
Program Command Succeeded
Downloading 0x00001CF0 bytes to be programmed at 0x00003310
Executing program ....
Program Command Succeeded
cmdwin::fl::device -d "FTFL_DFlash32S1RAM16" -o "8Kx32x1" -a 0x10000000 0x10007fff
cmdwin::fl::image -f "C:\\Users\\micha\\Downloads\\0244_k20dx_bl_0x5000.bin" -t "Auto Detect" -re on -r 0x10000000 0x10007fff -oe off
cmdwin::fl::erase image
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Image size is 0 bytes, nothing to erase.
Nothing to erase. No sectors selected
Erase Command Succeeded.
cmdwin::fl::write
-------------------------
Using restricted address range 0x10000000 to 0x10007FFF
Programming file C:\Users\micha\Downloads\0244_k20dx_bl_0x5000.bin
Auto-detection is successful.
File is of type Binary/Raw Format.

0 Bytes Programmed, Check Restricted Address Range
Program Command Succeeded

***************  END of OUTPUT

 

It seems as though nothing is programmed.  Hints as to what I am doing wrong would be appreciated.

Am I correct in thinking that a USB MSD should appear?  If not, how do I add k20dx_frdmk64f_if_crc_legacy_0x5000.bin  ?

 

Also,  am  I correct in thinking that if I cut the trace on J11, I can disable the openSDA stuff and use my multilink instead?

 

Thanks for reading

Michael

Outcomes