AnsweredAssumed Answered

Failing to get multicore_blinky_m0app running on LPC4370

Question asked by Simon Prentice on Jul 9, 2018
Latest reply on Mar 26, 2020 by Andrea Bettati
Sorry for such a newbie question, but ...
I have two LPC Link-2 boards.
One to act as the debug link and one to be the target.
Following the instructions in "Using an LPC-Link2 as an LPC4370 evaluation board" I programmed the debug board with CMSIS-DAP and then tried to debug the application.
It builds fine but trying to debug I get the errors shown below.
Any ideas?

2* LPC Link-2 boards
Debug board programmed with LPCScrypt->Program LPC-Link2 with CMSIS-DAP
Debug board J1 fitted
Target board no jumpers fitted
JTAG from J7 (debug) to J2 (target)
MCUXpresso IDE v10.2.0 [Build 759] [2018-05-15]
13:58:46 **** Incremental Build of configuration Debug for project multicore_blinky_m0app ****
make -r -j4 all
make: Nothing to be done for `all'.
13:58:47 Build Finished (took 484ms)
Debug As
MCUXpresso IDE LinkServer (inc. CMSIS-DAP) probes
Problem Occurred
'Launching multicore_blinky_m0app LinkServer Debug' has encountered a problem.
Error in final launch sequence.
Error in final launch sequence
Failed to execute MI command:
-target-select extended-remote | crt_emu_cm_redlink -msg-port=57570 -g -mi -2 -pLPC4370-M0 -vendor=NXP -reset= -ProbeHandle=1 -CoreIndex=1 -cache=disable -x C:/nxp/workspace/multicore_blinky_m0app/Debug --telnet 3330
Error message from debugger back end:
Remote communication error.  Target disconnected.: Success.
Remote communication error.  Target disconnected.: Success.
Error reported by target
Target Reported Errors
03: Failed on chip setup
03: Failed on chip setup
Canno halt processor.
Debugging context: multicore_blinky_m0app LinkServer Debug
MCUXpresso IDE RedlinkMulti Driver v10.2 (May 10 2018 18:10:59 - crt_emu_cm_redlink build 510)
Found chip XML file in C:/nxp/workspace/multicore_blinky_m0app/Debug\LPC4370-M0.xml
(  5) Remote configuration complete
Reconnected to existing link server
Connecting to probe 1 core 0:1 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.182 (NXP Semiconductors)
Serial Number:  JXBUJXKT
VID:PID:  1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&124e960f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0:1 after searching for a good core
Cannot halt processor
Cannot halt processor
debug interface type      = Cortex-M0 (DAP DP ID 0BA01477) over JTAG TAP 1
processor type            = Cortex-M0 (CPU ID 00000C20) on DAP AP 0
number of h/w breakpoints = 2
number of flash patches   = 0
number of h/w watchpoints = 1
Probe(0): Connected&Reset. DpID: 0BA01477. CpuID: 00000C20. Info: <None>
Debug protocol: JTAG. RTCK: Disabled. Vector catch: Disabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB471 ROM dev (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB008 ChipIP dev SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04000BB00A ChipIP dev DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04000BB00B ChipIP dev FPB (type 0x0)
Cannot halt processor
Failed on chip setup: Ep(04). Cannot halt processor.