Unable to unlock MKL26z64vft4

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Unable to unlock MKL26z64vft4

7,105 Views
dileeptn
Contributor I

hai,

we are using the MKL26z64vft4 in our latest project.And presently facing a issue while debugging the IC with J-Link and U-link.Presently we are using keil and while debugging a window pop 's up and shows the following text.

"Kinetis Device is locked! Do you want to unlock it ?

mass erase will be executed!".

After that we pressed the "ok " button to proceed further with mass erasing of the device.But unfortunately Another window pop-ed up with the following message

" Cannot Access Memory (@ 0xf0002FF0, read, acc size: 4 byte)".

We further proceed by pressing ok button on the pop-up window.And further another window appeared with the following information starting with an yellow triangle with exclamatory mark

" error : flash download failed - target DLL has been cancelled".

Since we had no other option we further proceed with the ok button.Could you please suggest the possible reasons which could lead to the error shown above? How should we move forward with the debugging of the IC.Please suggest us the steps and procedures to be followed to overcome this issue while debugging thee board.Is there any hardware wise setup which we should check whether we have implemented in our design which could have lead to such an error? Am looking forward to hear from you.....................

MCU used : MKL26Z64VFT4

Software : Keil

Programmer : U-link v2 and J-link

Problem : Unable to unlock MKL26Z series MCU

Is there is any specific method available to unlock kinetis series mcu.What is your suggestion?

Any help will be appreciated.

Labels (1)
0 Kudos
Reply
7 Replies

5,756 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi DILEEP T N,

Thank you for your interest in NXP kinetis product, I would like to provide service for you.
I find you also create a lot of community posts about this question.
Actually, the JLINK Commander is the good tool to check whether your KL26 hardware have problems or not.
Your KL26 board should be the new board which is designed by yourself.
Please check your hardware about these points at first:
1. SWD_DIO, add external 4.7K to 10K pull up resistor. SWD_CLK don't add external circuit.
2. RESET_b pin, should add 4.7K to 10K pull up resistor, and 0.1uf Capacitor to ground.
3. NMI pin should add external 4.7K to 10K pull up resistor.
4. please check your chip solder temperature, the datasheet defined the max temperature is 270 degree, if too high, it may damage your chip pin, this will also can't recoginize the chip.
Then, follow my attached picture do the unlock again with JLINK COMMANDER, debugger is JLINK:
You can use the: unlock kinetis
To unlock the chip.
Check my attached picture.
If you can't unlock it, please hold on the reset pin, then do the unlock kinetis again.
If your hardware have modified, the SWD interface connection is also correct, and you still can't unlock it.
I am afraid, your chip maybe damaged.
Please read this document, check the detail information:

https://community.nxp.com/servlet/JiveServlet/download/857127-1-396709/Kinetis%20Lock%20issue%20anal... 
Check what's the point you didn't matched?
Normally, if you don't lock it with your code, the new board with new chip meet this problem, normally the hardware problem.
If all the method can't unlock it, I think you can replace a new chip to your board, and try again.

Wish it helps you.
If you still have questions, please let me know.


Have a great day,
Kerry

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

5,756 Views
dileeptn
Contributor I

Hi Kerry thanks for your replay. I have tested the board using the document given by you. and unfortunately its not unlocked. Here i have attached the file in which i added errors i got using jlink commander and jlink. Please find the attachments with this replay. What is your suggestion about that?

Thanks

0 Kudos
Reply

5,756 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi DILEEP T N,

    I have checked your attached document, page 9, not correct, you can't input the unlock kinetis before you connect it.

  Please go to page 7, you need to input unlock kinetis under page7.

     Please connect the RESET pin in the SWD interface, which is connect to the JLINK, do unlock kinetis with reset hold on and not hold on.

    If all these can't unlock it, I am afraid two issue may on your side:

1. your lock the chip and even disable the mass erase bit.

2. Your chip is damaged

    All these points, I highly recommend you don't try it any more, don't waste the time, please change another chip and test it again. Now, how many board on your side have this problem.? When you solder the chip, please take care the temperature, from my own experience, a lot of customer damaged the chip when they use too high solder temperature, it's better about 300 degree, actually, the datasheet defined solder temperature is just 270 degree.


Have a great day,
Kerry

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

0 Kudos
Reply

5,755 Views
yongzheng_lv
Contributor I

hi kerry zhou

i can't connect mcu, Can you help me analyze the reason?

J-Link>unlock
Syntax: unlock <DeviceName>
---Supported devices---
LM3Sxxx [<Auto>]
Kinetis
EFM32Gxxx
LPC5460x
J-Link>unlock kinetis
Found SWD-DP with ID 0x2BA01477
Unlocking device...O.K.
J-Link>connect
Device "S32K144" selected.


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.
Found SW-DP with ID 0x2BA01477
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
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.
Found SW-DP with ID 0x2BA01477
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
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.
Found SW-DP with ID 0x2BA01477
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
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.
Found SW-DP with ID 0x2BA01477
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
Cannot connect to target.
J-Link>

0 Kudos
Reply

5,581 Views
kerryzhou
NXP TechSupport
NXP TechSupport

Hi yongzheng_lv,

  Please create your own question in a new question post.

  Please tell us what the kinetis chip partnumber you are using, it is your own design board, your smallest system schematic.

  After you create the new question post, we will reply you directly in the new post, please don't follow the other's old post, thanks a lot for your understanding.

 

Best Regards,

Kerry

0 Kudos
Reply

4,867 Views
ljmljmljm
Contributor II

I met the same problem as him, using s32k148 chip. Was this problem solved later?

0 Kudos
Reply

4,865 Views
kerryzhou
NXP TechSupport
NXP TechSupport

create the new question post, then the related engineer will help you!

 

0 Kudos
Reply