AnsweredAssumed Answered

LPC54018 : Unable to start debugging from main()

Question asked by Sreevishakh kp on Jun 26, 2019
Latest reply on Jun 30, 2019 by Alice_Yang

IDE-MCUEXpresso, Controller - LPC 54018 (180 PIN), Development Board - OM40003 (LPCXpresso54018)

 

I am using "EOL_Programmer LinkServer Debug.launch" for debugging. I am trying to debug my application. But unable to start debugging from main().

 

 

Console Log:

 

MCUXpresso IDE RedlinkMulti Driver v10.3 (Feb 7 2019 22:50:02 - crt_emu_cm_redlink build 760)
Found chip XML file in C:/Users/aakashd.DANLAWTECH/Documents/MCUXpressoIDE_10.3.1_2233/workspace/54018_INIT_PHASE/EOL_Programmer/Debug\LPC54018.xml
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: BRA5BQER
VID:PID: 1FC9:0090
USB Path: \\?\hid#vid_1fc9&pid_0090&mi_00#7&38ef1090&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
Using memory from core 0 after searching for a good core
On debug connection reset using system reset
debug interface type = Cortex-M3/4 (DAP DP ID 2BA01477) over SWD TAP 0
processor type = Cortex-M4 (CPU ID 00000C24) on DAP AP 0
number of h/w breakpoints = 6
number of flash patches = 2
number of h/w watchpoints = 4
Probe(0): Connected&Reset. DpID: 2BA01477. CpuID: 00000C24. Info: <None>
Debug protocol: SWD. RTCK: Disabled. Vector catch: Enabled.
Content of CoreSight Debug ROM(s):
RBASE E00FF000: CID B105100D PID 04000BB4C4 ROM (type 0x1)
ROM 1 E000E000: CID B105E00D PID 04000BB00C Gen SCS (type 0x0)
ROM 1 E0001000: CID B105E00D PID 04003BB002 Gen DWT (type 0x0)
ROM 1 E0002000: CID B105E00D PID 04002BB003 Gen FPB (type 0x0)
ROM 1 E0000000: CID B105E00D PID 04003BB001 Gen ITM (type 0x0)
ROM 1 E0040000: CID B105900D PID 04000BB9A1 CSt TPIU type 0x11 Trace Sink - TPIU
ROM 1 E0041000: CID B105900D PID 04000BB925 CSt ETM type 0x13 Trace Source - Core
NXP: LPC54018
DAP stride is 4096 bytes (1024 words)
( 65) Chip Setup Complete
Connected: was_reset=false. was_stopped=true
Awaiting telnet connection to port 3333 ...
GDB nonstop mode enabled

 

Debug Console Output:

 

GNU gdb (GNU Tools for Arm Embedded Processors 7-2018-q2-update) 8.1.0.20180315-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word".

Program stopped.
0x03000144 in ?? ()

Program received signal SIGSTOP, Stopped (signal).
0x03000966 in ?? ()

 

I am unable to start debugging from main().

 

Kindly revert back if you have any solution.

Outcomes