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

[ricardot_s]

We are not able to program this 32K device, the error is received after try program the device using LPC_link2, when we use the same LPC_link2 with the MKE15Z256 chip it works fine.. I see that the driver changes, maybe, it would be the problem, can you please check this issue?

MCUXpresso IDE RedlinkMulti Driver v11.0 (Aug 27 2019 16:46:33 - crt_emu_cm_redlink build 22)
Found chip XML file in E:/Proj_McuExpresso/Exemplos/MKE14Z32xxx4_Project/Debug\MKE14Z32xxx4.xml
Reconnected to existing LinkServer process.
============= SCRIPT: kinetisconnect.scp =============
Kinetis Connect Script
Connecting to Probe Index = 1
This probe = 1
This TAP = 0
This core = 0
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.224 (NXP Semiconductors)
Serial Number:  BSEWKSCR
VID:PID:  1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&1230f8ff&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 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: MKE14Z32xxx4
DAP stride is 1024 bytes (256 words)
Inspected v.2 On chip Kinetis Flash memory module FTFA_1K.cfx
Image 'Kinetis SemiGeneric Aug 27 2019 15:36:49'
Opening flash driver FTFA_1K.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 0x20000F58
Warning - failed to initialize mailbox (at 0x20000F48) - rc Em(12). Target rejected debug access at location 0x20000F48
Flash Driver V.2 startup failed - rc Em(12). Target rejected debug access at location 0x20000F48
chip initialization failed - Em(12). Target rejected debug access at location 0x20000F48
failed to initialize flash driver FTFA_1K.cfx

[lpcxpresso_supp]

Hi Ricardo,

Further to the reply above - investigations have highlighted another issue that will prevent the __Tiny flash driver working on this part (unfortunately we don't have every MCU available for testing).

Please bear with us while we continue to investigate.

Yours,

MCUXpresso IDE Support

[ricardot_s]

Hi,

We have solved in another way.. we just changed the firmware of the lpc-link2 to act as a jlink segger and it works for us.

Anyway, thank you for your help.

Get Outlook for Android<https://aka.ms/ghei36>

[lpcxpresso_supp]

I am glad you have worked around this problem - and apologise for this inconvenience.

For completeness:

The failure mode for the __Tiny driver on this MKExx part is because the small footprint code sacrificed the ability to differentiate between KE and KL watchdog handling - which wasn't an original requirement for this driver.

A flash programming solution for this 4K RAM part with LinkServer CMSIS/DAP will be introduced into the next release of MCUXpresso IDE.

Yours,

MCUXpresso IDE Support

[lpcxpresso_supp]

Hi Ricardo,

Thank you for your report. Upon investigation I can see that the SDK for this part specifies a flash driver called FTFA_1K.cfx. This flashdriver uses RAM beyond the range supported on this device.

The appropriate flashdriver for this part should be FTFA_1K_Tiny.cfx - fortunately, this driver is supplied with the IDE and can be selected for your project...

To do this, right click on your project and select 'Properties'. From the dialogue (shown below), select MCUSettings and click the '...' in the Driver Column. From the LinkServer flash driver dialogue, select the FTFA_1K_Tiny.cfx flash driver and click OK -> Apply and Close.  This will associate the new driver with your project.

Further, I will look to correcting the SDK for this part.

Yours,

MCUXpresso IDE Support