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

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

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

1,646 Views
emmaka63
Contributor I

I'm using MCUXpresso IDE v11.0.1 [Build 2563] [2019-09-01] with LPC-Link2 debug probe and a MKE04Z8VTG4 MCU. 

It is not possible to get a connection to the mcu.

MCUXPresso reports:

Driver memory check after reset - mem not working after mailbox read - Em(12). Target rejected debug access at location 0x20001770
chip initialization failed - Em(12). Target rejected debug access at location 0x20000300
failed to initialize flash driver FTFE_2K_KE.cfx
( 65) Chip Setup Complete
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

The whole report:

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number: BYGWGRAV
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#8&e4f0ec4&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 = Cortex-M0+ (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 E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
ROM 2 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
ROM 2 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
ROM 2 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
NXP: MKE04Z8xxx4
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Kinetis Flash memory module FTFE_2K_KE.cfx
Image 'Kinetis SemiGeneric Aug 27 2019 15:36:56'
Opening flash driver FTFE_2K_KE.cfx
Sending VECTRESET to run flash driver
Driver memory check after reset - mem not working after mailbox read - Em(12). Target rejected debug access at location 0x20001770
chip initialization failed - Em(12). Target rejected debug access at location 0x20000300
failed to initialize flash driver FTFE_2K_KE.cfx
( 65) Chip Setup Complete
(100) Target Connection Failed
Unable to perform operation!
Command failed with exit code 1

What can I do? It seems to be a problem with the small memory, because the target rejected debug access from a non existing memory area.

Do you have a solution for me?

0 Kudos
5 Replies

1,335 Views
satbir7
Contributor III

Just wanted to update, that Debugging works fine with the new MCUXpresso IDE v11.2.1 [Build 4149] [2020-10-07] and SDK version of 2.8.0. 

0 Kudos

1,410 Views
diego_charles
NXP TechSupport
NXP TechSupport

Hello, Emanuel

Thanks to report your problem. I've tried to replicate your problem,   I also couldn't debug with CMSIS-DAP.  Did you had trouble with the JLINK firmware for the probe?

Have a great day,
Diego

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

0 Kudos

1,410 Views
emmaka63
Contributor I

Hello Diego,

yes, it works with the J-LINK firmware. 

Regards,

Emanuel

0 Kudos

1,410 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Thank you for the report, we'll investigate.

Regards,

MCUXpresso IDE Support

0 Kudos

1,380 Views
satbir7
Contributor III

Seems like this hasn't been resolved yet.

I am having the same issue on a MKE02Z64M. Jlink firmware works fine on the Link V2.

But CMSIS-DAP can not establish a connection....

 

Any workarounds ?

Thanks,
Satbir

 

 

0 Kudos