topic MK64F512x chip readout protection in Kinetis Microcontrollers

MK64F512x chip readout protection

chhsu0229 — Tue, 07 Dec 2021 07:42:19 GMT

How can I remove the readout protection?

InitTarget()
Protection bytes in flash at addr. 0x400 - 0x40F indicate that readout protection is set.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash.
Executing default behavior previously saved in the registry.
Device will be unsecured now.
Timeout while unsecuring device. Erase never starts.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
DPv0 detected
Scanning AP map to find all available APs
AP[2]: Stopped AP scan as end of AP map has been reached
AP[0]: AHB-AP (IDR: 0x24770011)
AP[1]: JTAG-AP (IDR: 0x001C0000)
Iterating through AP map to find AHB-AP to use
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
AP[1]: Skipped. Not an AHB-AP

****** Error: Could not find core in Coresight setup

Re: MK64F512x chip readout protection

PabloAvalos — Thu, 16 Dec 2021 21:50:47 GMT

Hi, @chhsu0229

Many thanks for your patience.

Hoping you are well, the method to remove the readout protection can be done by using the GUI Flash Tool that our MCUXpresso IDE supports, and another method can be used is by the SEGGER J-Link Commander.

Here you will find the way to do it using any option that you prefer: https://community.nxp.com/t5/Kinetis-Microcontrollers/MK20DX256VLH7-Jlink-Problem-readout-protection/m-p/1259854/highlight/true

Please let me know if you have more questions.

Best Regards,

Pablo Avalos.

Re: MK64F512x chip readout protection

chhsu0229 — Fri, 17 Dec 2021 09:18:31 GMT

Hi PabloAvalos,

It doesn't work.

Thanks

Re: MK64F512x chip readout protection

PabloAvalos — Fri, 17 Dec 2021 20:31:20 GMT

Hi, @chhsu0229

Hoping you are excellent.

I would like to share with you another alternative that may be help you:

https://community.nxp.com/t5/Kinetis-Microcontrollers/Unable-to-unlock-MKL26z64vft4/m-p/749297

Also you can check this guide: Kinetis Lock Issue analysis and unlock way.pdf that it is included into the thread of our community that I provided you above.

Please let me know if you have more questions.

Best Regards.

Pablo Avalos.

Re: MK64F512x chip readout protection

chhsu0229 — Sat, 18 Dec 2021 13:18:06 GMT

Hi,

I have tried the way that Kinetis Lock Issue analysis and unlock way.pdf. And, It is unable to unlock MK64F512x.

We produced 250pcs productions using MK64F512x, unfortunately, there are 38pcs were locked. We checked the chip solder temperature. it was ~ 285 degrees.

I tried to unlock the chip, all showed following debug message,

Connecting to target via SWD
InitTarget()
Protection bytes in flash at addr. 0x400 - 0x40F indicate that readout protectio
n is set.
For debugger connection the device needs to be unsecured.
Note: Unsecuring will trigger a mass erase of the internal flash.
Executing default behavior previously saved in the registry.
Device will be unsecured now.
Timeout while halting CPU.

Re: MK64F512x chip readout protection

PabloAvalos — Tue, 28 Dec 2021 14:15:56 GMT

Hi, @chhsu0229

Many thanks for your patience. Due to holidays the replies were delayed.

Regarding your chip solder temperature around 285 degrees, it is out of spec. You can check it right here: Kinetis K64 Package Quality Tab.

Did the chip reach this peak of 285 degrees of temperature in your production? Because might be damaged.

Please let me know.

Best Regards and Happy Holidays.

Pablo Avalos.