Issue regarding error which appeared during erasing MKL26Z64VFT4

dileeptn — Sat, 12 May 2018 15:52:36 GMT

Hai ,
We faced an issue in jlink command when trying to mass erase MKL26Z64VFT4. I have mentioned the error below.

Error:

SEGGER J-Link Commander V6.33a (Compiled May 9 2018 17:23:00)
DLL version V6.33a, compiled May 9 2018 17:22:41

Connecting to J-Link via USB...O.K.
Firmware: J-Link V9 compiled Apr 20 2018 16:47:26
Hardware version: V9.30
S/N: 269302709
License(s): FlashBP, GDB
OEM: SEGGER-EDU
VTref=3.322V

Type "connect" to establish a target connection, '?' for help
J-Link>connect
Please specify device / core. <Default>: MKL26Z64XXX4
Type '?' for selection dialog
Device>device mkl26z64xxx4
Please specify target interface:
J) JTAG (Default)
S) SWD
F) FINE
I) ICSP
C) C2
TIF>s
Specify target interface speed [kHz]. <Default>: 4000 kHz
Speed>1000 kHz
Device "MKL26Z64XXX4 (ALLOW SECURITY)" selected.

Connecting to target via SWD
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.
Found SW-DP with ID 0x0BC11477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: CUSTOM-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
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.
Found SW-DP with ID 0x0BC11477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: CUSTOM-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00

****** Error: Could not find core in Coresight setup
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.
Found SW-DP with ID 0x0BC11477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: CUSTOM-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
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.
Found SW-DP with ID 0x0BC11477
AP map detection skipped. Manually configured AP map found.
AP[0]: AHB-AP (IDR: Not set)
AP[1]: CUSTOM-AP (IDR: Not set)
AP[0]: Skipped. Invalid implementer code read from CPUIDVal[31:24] = 0x00
Cannot connect to target.

The above shown as mentioned above are the errors which were generated while trying to erase or unlock the IC.
I am not able to do any operation to the MKL IC and cant even access it either. It shows errors as shown above. I tried most of the techniques to mass erase the IC but finally landed nowhere. When i searched in NXP for the solution of the errors.....i found a reply for one of the questions that the IC is brick and can't be used.What are your suggestions regarding this? If the IC is not Brick what could be the possible issue behind such an error?We are presently using samples which were provided as per our request from the NXP.Is there any other software we should try to unlock or erase the IC.Since the Project is so urgent please kindly help me with this issue.

any help will be appreciated......

Re: Issue regarding error which appeared during erasing MKL26Z64VFT4

kerryzhou — Mon, 14 May 2018 05:23:07 GMT

Hi Customer,

This is the same question as your another post, please check that post, I already reply you:

Unable to unlock MKL26z64vft4

Have a great day,
Kerry

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

topic Re: Issue regarding error which appeared during erasing MKL26Z64VFT4 in Kinetis Microcontrollers

Issue regarding error which appeared during erasing MKL26Z64VFT4

Re: Issue regarding error which appeared during erasing MKL26Z64VFT4