AnsweredAssumed Answered

LPC11C24 ResetISR() error

Question asked by Federico Fiorini on Dec 19, 2018

Hello,
I'm developing an application using Deep Sleep mode with the LPC11C24 board.
As our setup we are using the LPCXpresso LPC-Link LPC11C24 Rev B board and MCUXpresso 10.2.

 

I just tried to work on the code for the deep sleep mode and I got this error message from the debugger:

 

15: Target error from Set break/watch: Et:96: Pseudo-address (0xFFFFFFxx) for EXC_RETURN is invalid (GDB error?)
Debugging context: bms LinkServer Debug

The error persists even after attempting an ISP Reset, which usually cleared all possible errors derived from misconfiguring Deep Sleep mode. 

 

Furthermore, it seems from the IDE that the execution stops at ResetISR() but I haven't called it in my code, so perhaps  is a board's problem.

 

Any suggestions on how to continue? Or how to solve this problem? 

 


EDIT: 
This is the full console output for the debug session:

 

[Started server]
[Connected on port 3025]
redlink> ProbeList
Index = 1
Manufacturer = NXP - LPC-Link
Description = LPC-Link Probe v1.3
Serial Number = WIN64HS12
VID:PID = 1FC9:0009
Path = Not Available
redlink> ProbeStatus
Index = 1
Manufacturer = NXP - LPC-Link
Description = LPC-Link Probe v1.3
Serial Number = WIN64HS12
VID:PID = 1FC9:0009
Path = Not Available
IsOpen = FALSE
WireInitialized = FALSE
WireProtocol = JTAG
CoresConfigured = FALSE
PacketSize = 512
Reference Count = 0
HasSWV = FALSE
HasETM = FALSE
HasJTAG = TRUE
HasSWD = TRUE
Probe Type = WINUSB
Probe Reference Count = 0
redlink> ProbeIsOpen 1
FALSE
redlink> ProbeOpenByIndex 1
Probe Handle 1 Open
redlink> WireIsConnected 1
FALSE
redlink> WireSwdConnect 1
DpID = 0BB11477
redlink> CoresConfigured 1
FALSE
redlink> CoreConfig 1
Number of CORES/TAPs = 1, Fully recognized: True


MCUXpresso IDE RedlinkMulti Driver v10.2 (Jul 25 2018 11:29:34 - crt_emu_cm_redlink build 555)
Reconnected to existing link server
Connecting to probe 1 core 0:0 (using server started externally) gave 'OK'
Probe Firmware: LPC-Link Probe v1.3 (NXP - LPC-Link)
Serial Number: WIN64HS12
VID:PID: 1FC9:0009
USB Path:
Using memory from core 0:0 after searching for a good core
debug interface type = Cortex-M0 (DAP DP ID 0BB11477) over SWD TAP 0
processor type = Cortex-M0 (CPU ID 00000C20) 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: 0BB11477. CpuID: 00000C20. Info: <None>
Debug protocol: SWD. 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)
Inspected v.2 On-chip Flash Memory LPC11_12_13_16K_2K.cfx
Image 'LPC11_12_13 (16K Flash, min 2K RAM) Jul 25 2018 11:23:11'
NXP: LPC11C12/301
Connected: was_reset=false. was_stopped=false
Awaiting telnet connection to port 3331 ...
GDB nonstop mode disabled (using allstop mode)
Opening flash driver LPC11_12_13_16K_2K.cfx
Sending VECTRESET to run flash driver
Writing 4400 bytes to address 0x00000000 in Flash
Erased/Wrote page 0-1 with 4400 bytes in 331msec
Closing flash driver LPC11_12_13_16K_2K.cfx
Flash Write Done
Flash Program Summary: 4400 bytes in 0.33 seconds (12.98 KB/sec)
Starting execution using system reset and halt target
Target error from Set break/watch: Et:96: Pseudo-address (0xFFFFFFxx) for EXC_RETURN is invalid (GDB error?)

Outcomes