LPC-Link2 debug probe not working in MCUXpresso with MKE16Z64VLF in CMSIS-DAP mode

Kaarthi · ‎07-27-2021

Hi,

I am working with MKE16Z64 microcontroller with LPC Link-2 debug probe. I am not able to debug the microcontroller.I am getting the follwing error,

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.361 (NXP Semiconductors)
Serial Number: KZB2NWIQ
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&31460cdb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
debug interface type = CoreSight DP (DAP DP ID 0BC11477) over SWD TAP 0
processor type = Cortex-M0+ (CPU ID 00000C60) on DAP AP 0
number of h/w breakpoints = 2
number of flash patches = 0
number of h/w watchpoints = 2
Probe(0): Connected&Reset. DpID: 0BC11477. CpuID: 00000C60. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE F0002000: CID B105100D PID 000008E000 ROM (type 0x1)
ROM 1 F0000000: CID B105900D PID 04001BB932 CSt ARM MTB type 0x31 Trace Sink - Basic trace router
ROM 1 F0001000: CID B105900D PID 000008E000 CSt MTBDWT type 0x4 Debug Control - Other
ROM 1 E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
ROM 4 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
ROM 4 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
ROM 4 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
NXP: MKE16Z64xxx4
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Kinetis Flash memory module FTFA_1K.cfx
Image 'Kinetis SemiGeneric Jul 12 2021 22:06:00'
Opening flash driver FTFA_1K.cfx
Sending VECTRESET to run flash driver
flash driver polled mailbox (8 bytes at 0x20000BF0) read failed (on poll 2/301) - retrying after 1ms - rc Em(12). Target rejected debug access at location 0x20000BF0
flash driver polled mailbox (8 bytes at 0x20000BF0) read failed (on poll 4/301) - retrying after 1ms - rc Em(12). Target rejected debug access at location 0x20000BF4
flash driver polled mailbox (8 bytes at 0x20000BF0) read failed (on poll 4/301) - halting for postmortem - rc Em(12). Target rejected debug access at location 0x20000BF0
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access
Cannot halt processor
failed to halt target for postmortem - rc Ep(04). Cannot halt processor.
failed to read registers - Ep(08). Cannot access core regs when target running.
Flash Driver V.2 startup failed - rc Em(12). Target rejected debug access at location 0x20000BF0
chip initialization failed - Em(12). Target rejected debug access at location 0x20000BF0
failed to initialize flash driver FTFA_1K.cfx

diego_charles · ‎07-27-2021

Hi @Kaarthi

Is this the first time that you are debugging this chip?

Try the GUI flash tool. You can perform an erase, and if the part was locked , you can unlock it.

On a similar fashion you can Try a quick recovery with the J-Link commander. Connect to the MKE16Z64 option (with allow security), select the SWD interface, then write unlock Kinetis and erase commands.

Also, If I am not mistaken, your part has a ROM bootloader. You could set the part into ROM bootloader, while the ROM bootloader execute, try a simple mass erase from the MCUXpresso IDE.

Let me know your results.

Diego.

Kaarthi · ‎07-27-2021

Hi Diego,

Yes, I am first time debugging this chip.

I have already this unlocking procedure with GUI Flash tool. Still its not working. Please tell me how to do a ROM bootloader thing.

Below is the console thing for unlocking,

Executing flash operation 'Resurrect locked Kinetis device' (Resurrect locked Kinetis device) - Tue Jul 27 22:59:52 IST 2021
Checking MCU info...
Scanning for targets...
Executing flash action...
MCUXpresso IDE RedlinkMulti Driver v11.4 (Jul 2 2021 12:03:47 - crt_emu_cm_redlink.exe build 1)
( 0) Reading remote configuration
Wc(03). No cache support.
Found chip XML file in C:/Users/karthi/Documents/MCUXpressoIDE_11.4.0_6224/workspace/MKE16Z4_Project/Debug\MKE16Z64xxx4.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
============= SCRIPT: kinetismasserase.scp =============
Kinetis Mass Erase Script
DpID = 0BC11477
Assert NRESET
Reset pin state: 00
Power up Debug
MDM-AP APID: 0x001C0020
MDM-AP System Reset/Hold Reset/Debug Request
MDM-AP Control: 0x0000001C
MDM-AP Status (Flash Ready) : 0x00000032
Part is not secured
MDM-AP Control: 0x00000014
Release NRESET
Reset pin state: 01
MDM-AP Control (Debug Request): 0x00000004
MDM-AP Status: 0x0001003A
MDM-AP Core Halted
============= END SCRIPT ===============================
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.361 (NXP Semiconductors)
Serial Number: KZB2NWIQ
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&31460cdb&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
( 30) Emulator Connected
( 40) Debug Halt
( 50) CPU ID
debug interface type = CoreSight DP (DAP DP ID 0BC11477) over SWD TAP 0
processor type = Cortex-M0+ (CPU ID 00000C60) on DAP AP 0
number of h/w breakpoints = 2
number of flash patches = 0
number of h/w watchpoints = 2
Probe(0): Connected&Reset. DpID: 0BC11477. CpuID: 00000C60. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE F0002000: CID B105100D PID 000008E000 ROM (type 0x1)
ROM 1 F0000000: CID B105900D PID 04001BB932 CSt ARM MTB type 0x31 Trace Sink - Basic trace router
ROM 1 F0001000: CID B105900D PID 000008E000 CSt MTBDWT type 0x4 Debug Control - Other
ROM 1 E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
ROM 4 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
ROM 4 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
ROM 4 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
NXP: MKE16Z64xxx4
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Kinetis Flash memory module FTFA_1K.cfx
Image 'Kinetis SemiGeneric Jul 12 2021 22:06:00'
Can't query uninitialized dynamic flash driver in attach mode - assuming base 0x0 len 0x10000
( 65) Chip Setup Complete
Connected: was_reset=true. was_stopped=true
( 70) License Check Complete

diego_charles · ‎07-28-2021

Hi @Kaarthi

Thank you for letting me know your results.

My apologies, your MKE16Z64VLF does not have Boot ROM, only MKE16Z devices with 128 and 256 of flash.

Ok, could please help me with the the following? :

1 Update the Firmware of your LPC-Link to the latest version. Download latest LPCscrypt and follow this guide Programming (LPC-Link2)

You could either load the FW for CMSIS DAP or J-Link. I also recommend you to try with the J-Link firmware and J-Link commander . See attached picture. If you are able to test with that tool and have issues , please provide me a picture.

2 Please review the SWD interface , it is recommended to add certain pull-resistors to increase robustness , as described in this thread

Kaarthi · ‎07-29-2021

Hi,

I am not able to program the LPC Link2 I am getting like this,

I checked the reference guide, it states to ensure the VCOM driver, so I checked it also as below,

So kindly guide me in this...

Regards,

kaarthi

diego_charles · ‎08-03-2021

Hi @Kaarthi

Thank you for letting me know your results. Did you continue to have more problems to update the LPC-Link 2? You could refer to section 8.2 My device DFU boots but then just prints ‘......’of the LPC-Link2 Debug Probe
Firmware Programming User guide.

Edit, if you where able to test with the J-Link commander, and still failed to access your MCU debug port, please share with us the log .

I sorry for my late reply .

Diego.