I have been trying to do dual core freertos blinky example on MCB4357 using MCUXpresso with Segger Jlink debugger. But i'm getting this error while debugging to the M0 core. Can anyone please help?
ERROR: Could not connect to target.
SEGGER J-Link GDB Server V6.20g Command Line Version
JLinkARM.dll V6.20g (DLL compiled Oct 20 2017 17:09:27)
Command line: -nosilent -swoport 2355 -select USB=158000655 -telnetport 2356 -singlerun -endian little -noir -speed auto -port 2357 -vd -device LPC4357_M0 -if SWD -halt -reportuseraction
-----GDB Server start settings-----
GDBInit file: none
GDB Server Listening port: 2357
SWO raw output listening port: 2355
Terminal I/O port: 2356
Accept remote connection: localhost only
Generate logfile: off
Verify download: on
Init regs on start: off
Silent mode: off
Single run mode: on
Target connection timeout: 0 ms
------J-Link related settings------
J-Link Host interface: USB
J-Link script: none
J-Link settings file: none
------Target related settings------
Target device: LPC4357_M0
Target interface: SWD
Target interface speed: auto
Target endian: little
Connecting to J-Link...
J-Link is connected.
Device "LPC4357_M0" selected.
Firmware: J-Link ARM V8 compiled Nov 28 2014 13:44:46
Hardware: V8.00
S/N: 158000655
OEM: IAR
Checking target voltage...
Target voltage: 3.26 V
Listening on TCP/IP port 2357
Connecting to target...ERROR: LPC43xx Cortex-M0 (connect): Cortex-M0 coprocessors are not available when using SWD interface.
ERROR: LPC43xx Cortex-M0 (connect): Cortex-M0 coprocessors are not available when using SWD interface.
ERROR: Could not connect to target.
Hi Ranjith,
I would reccomend you take a look to the chapter "17. Multicore projects" in the MCUXpresso User Guide, specially to the "Slave Project Debug" section for more information about the debug settings modifications needed when using SEGGER Debug.
Hope it helps!
Best Regards,
Carlos Mendoza
Technical Support Engineer
Thabks.. i will give it a try :smileyhappy: