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

cancel
Showing results for 
Search instead for 
Did you mean: 

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

Jump to solution
1,084 Views
philmcmillan
Contributor II

I am using LPC-Link2 as a debug probe connecting via SWD to a Kinetis MKL02Z8xxx4 mcu.

Everything works fine if I load J-Link firmware onto the LPC-Link2.

However, when I use CMSIS-DAP firmware, either via MCUXpresso software with DFU jumper removed, or with CMSIS-DAP loaded on the LPC-Link2 via LPCScrypt utility, I consistently receive errors when debugging.

MCU Xpresso reports the following:

"dev load - can't read flash info at 0x2000027C - Em(12). Target rejected debug access at location 0x20000300"

Note that the LPC-Link2 works perfectly with J-Link firmware loaded under MCUXpresso and also enumerates correctly as a USB device on my Win 10 machine (as can be seen below).

---

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number:  I3F4AXOR
VID:PID:  1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&23d7ed76&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
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 F0000000: CID B105900D PID 04000BB932 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: MKL02Z8xxx4
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Kinetis Flash memory module FTFA_1K_Tiny.cfx
Image 'Kinetis SemiGeneric Feb 17 2017 17:24:03'
Opening flash driver FTFA_1K_Tiny.cfx
Sending VECTRESET to run flash driver
dev load - can't read flash info at 0x2000027C - Em(12). Target rejected debug access at location 0x20000300
flash data has invalid version/device name size (16)
driver describes no sectors starting at 0x0
Flash Driver V.2 startup failed - rc Ef(58): Flash Driver describes no sectors at its base address
chip initialization failed - Ef(58): Flash Driver describes no sectors at its base address
failed to initialize flash driver FTFA_1K_Tiny.cfx

1 Solution
549 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Hi Phil,

We have investigated this report and identified an issue that can lead to a read occurring beyond the end of available RAM on these very small footprint parts - this leads to the error that you have reported.

Thank you for bringing this to our attention.

Yours,

MCUXpresso IDE Support

View solution in original post

4 Replies
550 Views
lpcxpresso_supp
NXP Employee
NXP Employee

Hi Phil,

We have investigated this report and identified an issue that can lead to a read occurring beyond the end of available RAM on these very small footprint parts - this leads to the error that you have reported.

Thank you for bringing this to our attention.

Yours,

MCUXpresso IDE Support

View solution in original post

549 Views
Armandas
Contributor I

It:s great that you know about the issue, but when can we expect a fix?

0 Kudos
549 Views
lpcxpresso_supp
NXP Employee
NXP Employee

This issue was fixed in the MCUXpresso IDE 10.3.1 release - made in Feburary 2019 and mentioned in the release notes as below:

* Fixed issue with LinkServer flash driver handling causing
  unnecessary memory accesses to be made, which could cause flash
  programming failures with some very RAM limited MCUs

Apologies for not posting the information back into this thread.

Yours,

MCUXpresso IDE Support

0 Kudos
549 Views
Armandas
Contributor I

Hi. Thank you for the reply.

I am using MCUXpresso IDE v11.0.1 [Build 2563] [2019-09-01], but I get the same sort of problem with MKE16Z32 MCU.

As per the original post, programming works fine with j-Link firmware.

0 Kudos