Debugging LPC55S69 using LinkServer stopped working

cancel
Showing results for 
Search instead for 
Did you mean: 

Debugging LPC55S69 using LinkServer stopped working

74 Views
Contributor I

I am working with an LPC55S69 eval PCB and have run into a snag with the built-in LinkServer debugger.

It was working fine until I tried using the "Erase Flash action using LinkServer" function. After that I can no longer debug using the LinkServer.  Each time I get the same error: 

Error in final launch sequence:

Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=51066 -g -mi -2 -pLPC55S69 -vendor=NXP --bootromstall 0x50000040 -ProbeHandle=1 -CoreIndex=1 -cache=disable --flash-hashing --flash-driver-reset SOFT -x C:/Users/pouellette/Documents/Coding/MCUEXpresso/LPC55S69_Project/Debug --flash-dir C:/nxp/MCUXpressoIDE_11.2.0_4120/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.2.0.202007070855/binaries/Flash --flash-dir C:/Users/pouellette/Documents/Coding/MCUEXpresso/.mcuxpressoide_packages_support/LPC55S69_support/Flash --telnet 3330
Error message from debugger back end:
Remote communication error. Target disconnected.: Success.
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=51066 -g -mi -2 -pLPC55S69 -vendor=NXP --bootromstall 0x50000040 -ProbeHandle=1 -CoreIndex=1 -cache=disable --flash-hashing --flash-driver-reset SOFT -x C:/Users/pouellette/Documents/Coding/MCUEXpresso/LPC55S69_Project/Debug --flash-dir C:/nxp/MCUXpressoIDE_11.2.0_4120/ide/plugins/com.nxp.mcuxpresso.tools.bin.win32_11.2.0.202007070855/binaries/Flash --flash-dir C:/Users/pouellette/Documents/Coding/MCUEXpresso/.mcuxpressoide_packages_support/LPC55S69_support/Flash --telnet 3330
Error message from debugger back end:
Remote communication error. Target disconnected.: Success.

I noticed this thread which suggested changing the LinkServer Debug "Flash driver reset handling" and the behavior was the same with each setting

https://community.nxp.com/t5/LPC-Microcontrollers/FreeRTOS-LPCXpresso55S69-Devboard-debugging-proble...

I am using MCUXpresso IDE v11.2.0 [Build 4120] [2020-07-09]

0 Kudos
3 Replies

61 Views
Contributor I

F.Y.I. My Segger J-Link works fine.

I grabbed a fresh LPC55S69 Eval PCB and it behaves exactly the same way.

Note: I am able to perform ISP using the LinkServer. I am unable to debug using the the LinkServer.

 

0 Kudos

44 Views
NXP TechSupport
NXP TechSupport

Hello Philipouellette,

Have you tried loading the  debug firmware again? You can flash this firmware easily using the LPCScrypt tool (available in the link below).

https://www.nxp.com/design/microcontrollers-developer-resources/lpc-microcontroller-utilities/lpcscr...

I hope that this information helps!

Regards,
Gustavo

0 Kudos

63 Views
Contributor I

Contents of Console after attempting to debug.

 

MCUXpresso IDE RedlinkMulti Driver v11.1 (Jul 7 2020 10:48:32 - crt_emu_cm_redlink build 5)
Found chip XML file in C:/Users/pouellette/Documents/Coding/MCUEXpresso/LPC55S69_Project/Debug\LPC55S69.xml
( 5) Remote configuration complete
Reconnected to existing LinkServer process.
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number: ESAVBQCQ
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#b&1a3b00b9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 1 after searching for a good core
Cannot halt processor
Request debug reset of DAP
Cannot halt processor
Request debug reset of DAP
( 40) No Halt
debug interface type = Cortex-M33 (DAP DP ID 6BA02477) over SWD TAP 0
processor type = Cortex-M33 (CPU ID 00000D21) on DAP AP 1
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
Cannot halt processor
Failed on chip setup: Ep(04). Cannot halt processor.

0 Kudos