LPC5502 cannot load firmware

[pac60]

Hi all,

I get the error below loading the firmware on a LPC5502: the debug probe I'm using is MCU-link.

Any idea ?

Thank you in advance

Paolo

MCUXpresso IDE RedlinkMulti Driver v11.7 (Jan 12 2023 18:05:45 - crt_emu_cm_redlink build 1)

Found chip XML file in C:/Users/pcrem/Documents/MCUXpressoIDE_11.7.0_9198/workspace-5502/lpcxpresso55s02_ctimer_match_interrupt_example/Debug\LPC5502.xml

(  5) Remote configuration complete

Reconnected to existing LinkServer process.

Probe Firmware: LPC-LINK2 CMSIS-DAP V5.361 (NXP Semiconductors)

Serial Number:  FTCQPUEW

VID:PID:  1FC9:0090

USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&6722999&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 6BA02477) over SWD TAP 0

processor type            = Cortex-M33 (CPU ID 00000D21) on DAP AP 0

number of h/w breakpoints = 8

number of flash patches   = 0

number of h/w watchpoints = 4

Probe(0): Connected&Reset. DpID: 6BA02477. CpuID: 00000D21. Info: <None>

Debug protocol: SWD. RTCK: Disabled. Vector catch: Disabled.

Content of CoreSight Debug ROM(s):

RBASE E00FE000: CID B105100D PID 0000095000 ROM (type 0x1)

ROM 1 E00FF000: CID B105100D PID 04000BB4C9 ROM (type 0x1)

ROM 2 E000E000: CID B105900D PID 04000BBD21 CSt ARM ARMv8-M type 0x0 Misc - Undefined

ROM 2 E0001000: CID B105900D PID 04000BBD21 CSt ARM DWTv2 type 0x0 Misc - Undefined

ROM 2 E0002000: CID B105900D PID 04000BBD21 CSt ARM FPBv2 type 0x0 Misc - Undefined

ROM 2 E0000000: CID B105900D PID 04000BBD21 CSt ARM ITMv2 type 0x43 Trace Source - Bus

ROM 1 E0040000: CID B105900D PID 04000BBD21 CSt type 0x11 Trace Sink - TPIU

NXP: LPC5502

DAP stride is 1024 bytes (256 words)

Inspected v.2 On chip Flash memory using IAP lib LPC550x.cfx

Image 'LPC550x Jan 13 2023 11:55:03'

Opening flash driver LPC550x.cfx

VECTRESET requested but ARMv8 CPUs lack VCATCH. Using SOFTRESET instead

Using SOFT reset to run the flash driver

Flash variant 'LPC550x (64' detected (64KB = 128*512 at 0x0)

Closing flash driver LPC550x.cfx

Connected: was_reset=true. was_stopped=false

Awaiting telnet connection to port 3330 ...

GDB nonstop mode enabled

Opening flash driver LPC550x.cfx (already resident)

VECTRESET requested but ARMv8 CPUs lack VCATCH. Using SOFTRESET instead

Using SOFT reset to run the flash driver

Flash variant 'LPC550x (64' detected (64KB = 128*512 at 0x0)

Writing 24436 bytes to address 0x00000000 in Flash

Sectors written: 0, unchanged: 48, total: 48

Erased/Wrote sector 0-47 with 24436 bytes in 58msec

Closing flash driver LPC550x.cfx

Flash Write Done

Flash Program Summary: 24436 bytes in 0.06 seconds (411.44 KB/sec)

Starting execution using system reset and halt target with a stall address

Retask read watchpoint 1 at 0x50000040 to use for boot ROM stall

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

Warning - processor did not halt - gave up waiting

flash - system reset failed - Ep(04). Cannot halt processor.

Target error from Commit Flash write: Ep(04). Cannot halt processor.

GDB stub (C:\nxp\MCUXpressoIDE_11.7.0_9198\ide\plugins\com.nxp.mcuxpresso.tools.bin.win32_11.7.0.202301121712\binaries\crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.

state - running or following reset request - re-read of state failed - rc Nn(05). Wire ACK Fault in DAP access

[ZhangJennie · Accepted solution]

Hi pac60 

Please check issue with below steps:

1. Check driver:

Please make sure MCU-Link is well installed with following below start guide:

https://www.nxp.com/document/guide/getting-started-with-the-mcu-link:GS-MCU-LINK

Can you see MCU-Link device is recognized in windows manager window as shown in 1.3?

2. Check board:

Test MCU-Link with another board, if the problem is the same for all boards.

3. Check project

Create a NEW project under a NEW workspace, test if the project can be connected by MCU-Link?

Have a nice day,

Jun Zhang