topic Re: K66F MCU gets blocked. No communication possible in Kinetis Microcontrollers

K66F MCU gets blocked. No communication possible

alejandrosancho — Tue, 14 Jan 2020 17:29:08 GMT

I was trying to upload code through a bootloader we've implemented on our k66f and after loading the firmware we wanted to update, it enters in an state in which we cannot connect any more with it.

This is the script I get through J-link Commander:

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.
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 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 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 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 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 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 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.

It has already happened 3 times and we cannot recover from this state. I've tried to send: unlock Kinetis on J-link commander as well as reset the "reset" pin in the J-link commander. And there is no way to recover it. I do not know what steps lead to this situation and I cannot replicate it.

Thanks in advance for the help.

Re: K66F MCU gets blocked. No communication possible

kerryzhou — Wed, 15 Jan 2020 09:40:33 GMT

Hi alejandrosancho,

What's the board you are using? The official board or your own designed board?

If the unlock kinetis also can unlock it, maybe your chip is secured to the highest level.

Please check this document at first:

https://community.nxp.com/servlet/JiveServlet/download/857127-1-396709/Kinetis%20Lock%20issue%20analysis%20and%20unlock%…

Any updated information, please kindly let me know.

Have a great day,
Kerry

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

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you have a related question at a later point in time.
-------------------------------------------------------------------------------

Re: K66F MCU gets blocked. No communication possible

alejandrosancho — Wed, 15 Jan 2020 10:11:18 GMT

Hi Kerry, thanks for the response.

We are using a MK66FN2m0xxx18 and yes, it is our own PCB.

Re: K66F MCU gets blocked. No communication possible

alejandrosancho — Wed, 15 Jan 2020 10:51:36 GMT

It seems that we can find the SWD-DP interface which puts us on step 6. However, the script outputed from the reset pin script is the following:

J-Link connection not established yet but required for command.
Connecting to J-Link via USB...O.K.
Firmware: J-Link V10 compiled Jan 7 2020 16:51:47
Hardware version: V10.10
S/N: 50114001
License(s): GDB
VTref=3.303V
Selecting 1000 kHz as target interface speed

Sleep(10)

Target connection not established yet but required for command.
Please specify device / core. <Default>: MK66FN2M0XXX18
Type '?' for selection dialog
Device>
Please specify target interface:
J) JTAG (Default)
S) SWD
T) cJTAG
TIF>
Device position in JTAG chain (IRPre,DRPre) <Default>: -1,-1 => Auto-detect
JTAGConf>
Device "MK66FN2M0XXX18" selected.

Connecting to target via JTAG
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 halting CPU.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
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
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 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 halting CPU.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP

Target connection not established yet but required for command.
Device "MK66FN2M0XXX18" selected.

****** 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.
Timeout while halting CPU.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
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.
Readout protection is set and mass erase is disabled. J-Link cannot unprotect the device.
TotalIRLen = 4, IRPrint = 0x01
JTAG chain detection found 1 devices:
#0 Id: 0x4BA00477, IRLen: 04, CoreSight JTAG-DP
Cannot connect to target.

Sleep(1000)

Selecting SWD as current target interface.

Sleep(10)

Select SWD by sending SWD switching sequence.
Found SWD-DP with ID 0x2BA01477

Sleep(10)

Write DP register 2 = 0x01000000

Sleep(10)

Read AP register 0 = 0x00000000

Sleep(10)

Read AP register 0 = 0x00000037

Sleep(10)

Read AP register 1 = 0x00000037

Sleep(10)

Read AP register 1 = 0x00000000

Sleep(10)

Read AP register 0 = 0x00000000

Sleep(10)

Read AP register 0 = 0x00000037

Sleep(10)

Write AP register 1 = 0x00000001

Sleep(1000)

Read AP register 0 = 0x00000037

Sleep(10)

Read AP register 0 = 0x00000037

Sleep(10)

Read AP register 1 = 0x00000037

Sleep(10)

Read AP register 1 = 0x00000001

Sleep(100)

Write DP register 2 = 0x00000000

Sleep(1000)

Selecting JTAG as current target interface.

Sleep(100)

Target connection not established yet but required for command.
Device "MK66FN2M0XXX18" selected.

Script processing completed.

Re: K66F MCU gets blocked. No communication possible

kerryzhou — Thu, 16 Jan 2020 02:42:38 GMT

Hi alejandrosancho，

Please check your hardware these points:

1. NMI pin add the external 4.7K pullup resistor?

2. SWD_DIO need to add external 10K pull up

3. reset _b pin need to add external 10K pull up, and 0.1uf capacitor to ground.

BTW, do you try the SWD interface with the JLINK and JLINK commander window directly?

Please use the SWD, and unlock kinetis, then connect it again, can you find the arm core?

If you still can't find the ARM core, it means your hardware still have problems.

How many board you have test, all have the connection problems?

Whether you can connect it in the previous time, or just the new board, the first time connection is failure?

Have a great day,
Kerry

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

- We are following threads for 7 weeks after the last post, later replies are ignored
Please open a new thread and refer to the closed one, if you ha

Re: K66F MCU gets blocked. No communication possible

stephenlangstaf — Thu, 16 Jan 2020 11:07:27 GMT

Protection bytes in flash at addr. 0x400 - 0x40F indicate that readout protection is set.
For debugger connection the device needs to be unsecured

My guess is that these lines are important:

does your bootloader, or the application itself, write anything into 0x400..0x40F ?
Can you change your bootloader and application to report the contents of 0x400..0x40F ?

Re: K66F MCU gets blocked. No communication possible

robinwillis — Wed, 02 Mar 2022 19:12:02 GMT

This was helpful for my situation, thanks! I was getting the same error message and the solution was to pull NMI high. I am using the FRDM-K66F board and am trying to run it with P3V3 off (only P3V3_K66F on) in order to reduce power. The NMI is pulled up to P3V3 so this was the problem! Thanks again.