FRDM-k64F | Device FTMRH_PFlash64RAM4 is protected

[HariHaran4274]

Hi Community,

I am using FRDM-K64 board for past few months.
Unexpectedly when i try to flash that controller , it enumerates the following in the console.

fl::target -lc "yes"
fl::target -b 0x1ffffc00 0x1000
fl::target -v on -l off
cmdwin::fl::device -d "FTMRH_DFlash256S1RAM4" -o "256x32x1" -a 0x10000000 0x100000ff
cmdwin::fl::erase all
Beginning Operation ...
-------------------------
Performing target initialization ...
Device FTMRH_DFlash256S1RAM4 is protected
Erasing .............
Erase Command Succeeded.
Device FTMRH_DFlash256S1RAM4 is protected
cmdwin::fl::device -d "FTMRH_PFlash64RAM4" -o "16kx32x1" -a 0x0 0xffff
cmdwin::fl::image -f "C:\\Users\\vvsa\\Downloads\\gpio.bin" -t "Auto Detect" -re on -r 0x0 0xffff -oe off
cmdwin::fl::erase image
Beginning Operation ...
-------------------------
Auto-detection is successful.
File is of type Binary/Raw Format.

Device FTMRH_PFlash64RAM4 is protected
Erasing ..............
Erase Command Succeeded.
Device FTMRH_PFlash64RAM4 is protected
cmdwin::fl::write
-------------------------
Flash Operation. ...
Auto-detection is successful.
File is of type Binary/Raw Format.

Device FTMRH_PFlash64RAM4 is protected
Programming ....
Device FTMRH_PFlash64RAM4 is protected
Error: Program Command Failed.
Error: Program Command Failed.

Please suggest me a solution.

Thanks in Advance!!

[ZhangJennie]

Hi HariHaran4274,

If the on chip flash is secured. Thus any other debug interface can not access it.

I would suggest you check your source code if Flash Security Register is set by accident. You may create a brand new project to test if you experience the same problem with it while debugging.

There are several flash secure levels.

1. If the flash is secured by FSEC[SEC] bit only, user can unsecure the device by J-Link commander. Go to https://www.segger.com/ to download J-Link Commander. See attached video of how to use J-Link commander
2. If the flash is secured by SEC secure + MEEN(FSEC[MEEN] = 10) disable, attempts to mass erase via the debug interface are blocked. debugger interface can no longer unsecure flash by mass erase. Thus the chip can no longer be reprogrammed and revised. The flash can be only read by returning to the NXP factory.  I have many customer experienced this problem because MEEN is disabled.
3. If the flash is secured by SEC secure + FSLACC denied. It is similar like level 2 above, but even NXP factory cannot unsecure it.

Hope this helps,

Jun Zhang