AnsweredAssumed Answered

MCUXpresso IDE v10.3.0 [Build 2200] Problem [BUG?]

Question asked by Davaa Dorj on Dec 16, 2018
Latest reply on Feb 19, 2019 by Rex Lam

I just installed new version of MCUXpresso and can not debug.


MCUXpresso IDE v10.3.0 [Build 2200] [2018-12-03] (MacOSX 10.14.1)


Here is the console log:



MCUXpresso IDE RedlinkMulti Driver v10.3 (Nov 28 2018 02:37:51 - crt_emu_cm_redlink build 748)
Found part description in XML file LPC82x.xme
Reconnected to existing link server
Connecting to probe 1 core 0 (using server started externally) gave 'OK'
Probe Firmware: LPC-LINK2 CMSIS-DAP V5.224 (NXP Semiconductors)
Serial Number:  I3FSJUKQ
VID:PID:  1FC9:0090
USB Path: USB_1fc9_0090_14100000_ff00
Using memory from core 0 after searching for a good core
On debug connection reset using system reset
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 = 4
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: Enabled.
Content of CoreSight Debug ROM(s):
RBASE F0000000: CID B105100D PID 0500081000 ROM (type 0x1)
ROM 1 E00FF000: CID B105100D PID 04000BB4C0 ROM (type 0x1)
ROM 3 E000E000: CID B105E00D PID 04000BB008 Gen SCS (type 0x0)
ROM 3 E0001000: CID B105E00D PID 04000BB00A Gen DWT (type 0x0)
ROM 3 E0002000: CID B105E00D PID 04000BB00B Gen FPB (type 0x0)
DAP stride is 1024 bytes (256 words)
Inspected v.2 On-chip Flash Memory LPC800_32.cfx
Image 'LPC800 (32K) Oct 25 2018 11:57:50'
Connected: was_reset=true. was_stopped=false
Awaiting telnet connection to port 3330 ...
GDB nonstop mode enabled
Opening flash driver LPC800_32.cfx
SYSRESETREQ reset omitted - already reset
XPSR register failed - rc Ep(08). Cannot access core regs when target running.
Target error from Commit Flash write: Ep(08). Cannot access core regs when target running.
GDB stub (crt_emu_cm_redlink) terminating - GDB protocol problem: Pipe has been closed by GDB.