HI,
Has anyone encountered this problem and how did you fix it?
I am using Freescale Kinetis K24-256K device and Keil U-vision V5.15. Occasional - every few days the Device locks with error "Kinetis device is locked". when this happens there is no way to ever program this device again
Great care has been taken to assure that the startup files have the correct fuses set so that the device (specifically MASS ERASE) is not locked. Strangely this problem never occurs with the JLINK on another dev PC. I have recently installed onto a new PC, I also tried my backup ULINK2 probe.
All advice I have found relates to changing the RESET options in the ULINK Debug - Reset and Connect options. All this has been tried. Also all notes form Freescale on the device security has been studied. I have also made sure the Reset line is connect and pulls properly to the correct levels.
Any advice would be appreciated.
Even I'm facing the same problem with MK20DX256VLH7. My controller is new, fresh and blank in which I'm trying to flash the Blinky example .hex file but couldn't.
First I'm getting the Kinetics is locked and when I say mass erase OK, it says me back can't access memory.
The error which it shows is "Cannot access Memory (@ 0xe00ffff0, Read, Acc Size: 4 Byte)" but the the Build output it comes as "Cannot access Memory (@ 0x00000000, Write, Acc Size: 4 Byte)".
Kindly help as this is very critical need to resolve immediately.
Please see: http://www.keil.com/support/docs/3553.htm If this does not help, please let us know.
Yes i tried it but didn't work.
Again my device is locked kindly help as I'm loosing my valuable controller and time.
Hi,
I started this post and what I eventually found was 2 problems.
1. Bad ULINK, one of my ULINKs was not working properly and was clobbering the ERASE fuse 2. Build was wrong. I had a release build that shifted flash memory but did not init the boot area properly and so also clobbered the erase fuse.
Once I fixed these two problems I never again had a fuse lock that the reset procedure (changing ULINK connection options) could not recover from.