Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
See Also
Discussion Groups | LPC2000 | C++ debugging with OpenODC and eclipse
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
C++ debugging with OpenODC and eclipse - marc...@free.fr - Nov 16 13:01:43 2009
Hi,
I am getting less and less hair... I try to debug C++ whit Eclipse, OpenOCD (0.3.1), zylincdt (4.10.1) and a OLIMEX ARM USB jtag.
with c files everythin is working fine, and I can do start/stop step by step and everything in the source code.
But with a cpp source it complains that the source fine is not available. (debugging at assembly level is working)
Error message No source available for "main() "
some GDB info show that it sees the startup.s (although I cannot debug in either) but not any other file despite all directories are known. (main.cpp at root or /src doesn't change anything)
Any Ideas?
Thanks
Marcel
show dir
Source directories searched: D:/Projets/myproject;D:/Projets/myproject/.dep;D:/Projets/helisaver/inc;D:/Projets/myproject/inc/lpcinc;D:/Projets/myproject/out;D:/Projets/myproject/prj;D:/Projets/myproject/src;$cdir;$cwd
info files
Symbols from "D:\Projets\myproject\myproject_ROM.elf".
Local exec file:
`D:\Projets\myproject\myproject_ROM.elf', file type elf32-littlearm.
Entry point: 0x0 0x00000000 - 0x000048dc is .text
0x40000000 - 0x40000014 is .data
0x40000014 - 0x400010a0 is .bss
info sources
Source files for which symbols have been read in:
D:/Projets/myproject/Startup.s
Source files for which symbols will be read in on demand:
../../../gcc-4.0.2/gcc/config/arm/lib1funcs.asm, D:/Projets/myproject/swi_handler.s
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
I am getting less and less hair... I try to debug C++ whit Eclipse, OpenOCD (0.3.1), zylincdt (4.10.1) and a OLIMEX ARM USB jtag.
with c files everythin is working fine, and I can do start/stop step by step and everything in the source code.
But with a cpp source it complains that the source fine is not available. (debugging at assembly level is working)
Error message No source available for "main() "
some GDB info show that it sees the startup.s (although I cannot debug in either) but not any other file despite all directories are known. (main.cpp at root or /src doesn't change anything)
Any Ideas?
Thanks
Marcel
show dir
Source directories searched: D:/Projets/myproject;D:/Projets/myproject/.dep;D:/Projets/helisaver/inc;D:/Projets/myproject/inc/lpcinc;D:/Projets/myproject/out;D:/Projets/myproject/prj;D:/Projets/myproject/src;$cdir;$cwd
info files
Symbols from "D:\Projets\myproject\myproject_ROM.elf".
Local exec file:
`D:\Projets\myproject\myproject_ROM.elf', file type elf32-littlearm.
Entry point: 0x0 0x00000000 - 0x000048dc is .text
0x40000000 - 0x40000014 is .data
0x40000014 - 0x400010a0 is .bss
info sources
Source files for which symbols have been read in:
D:/Projets/myproject/Startup.s
Source files for which symbols will be read in on demand:
../../../gcc-4.0.2/gcc/config/arm/lib1funcs.asm, D:/Projets/myproject/swi_handler.s
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: C++ debugging with OpenODC and eclipse - Pete Vidler - Nov 17 3:53:37 2009
m...@free.fr wrote:
> with c files everythin is working fine, and I can do start/stop step by
> step and everything in the source code.
What compiler/linker settings did you use?
Does a simple C++ app (blinking LED, RS232, etc) work when programmed?
What GCC and GDB versions are you using?
Have you changed your startup and linker scripts to support C++?
Are you sure that you're linking with the 'g++' tool and *not* 'gcc' or
'ld' (because C++ has special linker requirements)?
Lots of unanswered questions.
I'm sure I have had C++ working before, but we don't use it much here so
it's been a while.
Pete
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> with c files everythin is working fine, and I can do start/stop step by
> step and everything in the source code.
What compiler/linker settings did you use?
Does a simple C++ app (blinking LED, RS232, etc) work when programmed?
What GCC and GDB versions are you using?
Have you changed your startup and linker scripts to support C++?
Are you sure that you're linking with the 'g++' tool and *not* 'gcc' or
'ld' (because C++ has special linker requirements)?
Lots of unanswered questions.
I'm sure I have had C++ working before, but we don't use it much here so
it's been a while.
Pete
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: C++ debugging with OpenODC and eclipse - marc...@free.fr - Nov 17 8:13:06 2009
Hi Pete
Thanks, compiling and linking is not a problem as my program is perfectly running, I just cannot do source code level debugging because the debugger doesn't find the source code.
>What compiler/linker settings did you use?
see makefile below, may be there is something missing to tell GDB where is the source code (I modified the makefile to have the source at project root without more success)
>Does a simple C++ app (blinking LED, RS232, etc) work when programmed?
my programm is working but not debbuging, a simple C app is debugging fine
>What GCC and GDB versions are you using?
Yagarto:
binutils: 2.18
gcc: 4.2.2
newlib: 1.16.0
gdb: 6.8.50-20080308-cvs
>Have you changed your startup and linker scripts to support C++?
link is working, but there may be an option to transmit source file to GDB?
>Are you sure that you're linking with the 'g++' tool and *not* 'gcc' or
>'ld' (because C++ has special linker requirements)?
yes.
>Lots of unanswered questions.
>
>I'm sure I have had C++ working before, but we don't use it much here so
>it's been a while.
you think I should switch to C ?
Thanks
Marcel
##############################################################################################
# Start of default section
#
TRGT = arm-elf-
CC = $(TRGT)gcc
CPP = $(TRGT)g++
CP = $(TRGT)objcopy
OD = $(TRGT)objdump
AS = $(TRGT)gcc -x assembler-with-cpp
HEX = $(CP) -O ihex
BIN = $(CP) -O binary
MCU = arm7tdmi
# List all default C defines here, like -D_DEBUG=1
DDEFS =
# List all default ASM defines here, like -D_DEBUG=1
DADEFS =
# List all default directories to look for include files here
DINCDIR =
# List the default directory to look for the libraries here
DLIBDIR =
# List all default libraries here
DLIBS =
#
# End of default section
##############################################################################################
##############################################################################################
# Start of user section
#
# Define project name here
PROJECT = myproject
# Define linker script file here
LDSCRIPT_RAM = .\prj\lpc2138-ram.ld
LDSCRIPT_ROM = .\prj\lpc2138-rom.ld
# List all user C define here, like -D_DEBUG=1
UDEFS = \
-DDEBUG=0 \
-DOS_LIBMODE_DP
# Define ASM defines here
UADEFS =
# List C source files here
CPPSRC = main.cpp
CPPSRC += rprintf.cpp
CPPSRC += sd_raw.cpp
CPPSRC += syscalls.cpp
CPPSRC += interrupt_utils.cpp
# List ASM source files here
ASRC = Startup.s
ASRC += swi_handler.s
# List all user directories here
UINCDIR = .\inc
UINCDIR += .\inc\lpcinc
# List the user directory to look for the libraries here
ULIBDIR =
# List all user libraries here
ULIBS =
# Define optimisation level here
OPT = -O0
#
# End of user defines
##############################################################################################
INCDIR = $(patsubst %,-I%,$(DINCDIR) $(UINCDIR))
LIBDIR = $(patsubst %,-L%,$(DLIBDIR) $(ULIBDIR))
DEFS = $(DDEFS) $(UDEFS)
ADEFS = $(DADEFS) $(UADEFS)
OBJS = $(CPPSRC:.cpp=.o) $(ASRC:.s=.o) $(CSRC:.c=.o)
CPPOBJ = $(CPPSRC:.cpp=.o)
LIBS = $(DLIBS) $(ULIBS)
MCFLAGS = -mcpu=$(MCU)
ASFLAGS = $(MCFLAGS) -g -gdwarf-2 -Wa,-amhls=$(<:.s=.lst) $(ADEFS)
CPFLAGS = $(MCFLAGS) $(OPT) -gdwarf-2 -fomit-frame-pointer -Wall -Wstrict-prototypes -fverbose-asm -Wa,-ahlms=$(<:.c=.lst) $(DEFS)
CPPFLAGS = $(MCFLAGS) $(OPT) $(CPPOPT) $(WARN) -Wa,-alms=$(<:.cpp=.lst) $(DEFS)
LDFLAGS_ROM = $(MCFLAGS) -nostartfiles -T$(LDSCRIPT_ROM) -Wl,-Map=$(PROJECT)_ROM.map,--cref,--no-warn-mismatch $(LIBDIR)
ODFLAGS = -x --syms
# Generate dependency information
CPFLAGS += -MD -MP -MF .dep\$(@F).d
CPPFLAGS += -MD -MP -MF .dep\$(@F).d
#
# makefile rules
#
all: ROM
ROM: $(OBJS) $(PROJECT)_ROM.elf $(PROJECT)_ROM.bin $(PROJECT)_ROM.hex $(PROJECT)_ROM.dmp
%o : %cpp
@echo "Compiling C++ $<"
@$(CPP) -c $(CPPFLAGS) -I . $(INCDIR) $< -o $@
%o : %c
@echo "Compiling $<"
@$(CC) -c $(CPFLAGS) -I . $(INCDIR) $< -o $@
%o : %s
@echo "Assembling $<"
@$(AS) -c $(ASFLAGS) $< -o $@
%ROM.elf: $(OBJS)
@echo "Linking $@"
@$(CC) $(OBJS) $(LDFLAGS_ROM) $(LIBS) -o $@
%hex : %elf
@echo "Create $@ from $<"
@$(HEX) $< $@
%bin : %elf
@echo "Create $@ from $<"
@$(BIN) $< $@
%dmp : %elf
@echo "Create $@ from $<"
@$(OD) $(ODFLAGS) $< > $@
clean:
-rm -f $(OBJS)
-rm -f $(PROJECT)_ROM.elf
-rm -f $(PROJECT)_ROM.map
-rm -f $(PROJECT)_ROM.hex
-rm -f $(PROJECT)_ROM.bin
-rm -f $(PROJECT)_ROM.dmp
-rm -f $(CSRC:.c=.c.bak)
-rm -f $(CSRC:.c=.lst)
-rm -f $(CSRC:.c=.o)
-rm -f $(CPPSRC:.cpp=.cpp.bak)
-rm -f $(CPPSRC:.cpp=.lst)
-rm -f $(CPPSRC:.cpp=.o)
-rm -f $(ASRC:.s=.lst)
-rm -f $(ASRC:.s=.o)
-rm -fR .dep
#
# Include the dependency files, should be the last of the makefile
#
-include $(shell mkdir .dep 2>/dev/null) $(wildcard .dep/*)
# *** EOF ***
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: C++ debugging with OpenODC and eclipse - Pete Vidler - Nov 17 8:19:17 2009
m...@free.fr wrote:
> >Are you sure that you're linking with the 'g++' tool and *not* 'gcc' or
> >'ld' (because C++ has special linker requirements)?
> yes.
Doesn't look like it to me:
> CC = $(TRGT)gcc
> CPP = $(TRGT)g++
...
> @echo "Linking $@"
> @$(CC) $(OBJS) $(LDFLAGS_ROM) $(LIBS) -o $@
Try using g++ to link -- I seem to remember this solving similar
problems in the past. G++ knows about C++ name mangling, which will
help when including debugging info, if I remember correctly.
Pete
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> >Are you sure that you're linking with the 'g++' tool and *not* 'gcc' or
> >'ld' (because C++ has special linker requirements)?
> yes.
Doesn't look like it to me:
> CC = $(TRGT)gcc
> CPP = $(TRGT)g++
...
> @echo "Linking $@"
> @$(CC) $(OBJS) $(LDFLAGS_ROM) $(LIBS) -o $@
Try using g++ to link -- I seem to remember this solving similar
problems in the past. G++ knows about C++ name mangling, which will
help when including debugging info, if I remember correctly.
Pete
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: C++ debugging with OpenODC and eclipse - marc...@free.fr - Nov 17 9:04:36 2009
>Try using g++ to link -- I seem to remember this solving similar
>problems in the past. G++ knows about C++ name mangling, which will
>help when including debugging info, if I remember correctly.
>
>Pete
didn't help Pete :-(
I did
%elf: $(OBJS)
@echo "Linking $@"
@$(CPP) $(OBJS) $(LDFLAGS_ROM) $(LIBS) -o $@
and result is the same. The must be a missing flag in that link command
regards
Marcel
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
>problems in the past. G++ knows about C++ name mangling, which will
>help when including debugging info, if I remember correctly.
>
>Pete
didn't help Pete :-(
I did
%elf: $(OBJS)
@echo "Linking $@"
@$(CPP) $(OBJS) $(LDFLAGS_ROM) $(LIBS) -o $@
and result is the same. The must be a missing flag in that link command
regards
Marcel
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: Re: C++ debugging with OpenODC and eclipse - Pete Vidler - Nov 17 9:09:38 2009
m...@free.fr wrote:
> ASFLAGS = $(MCFLAGS) -g -gdwarf-2 -Wa,-amhls=$(<:.s=.lst) $(ADEFS)
> CPFLAGS = $(MCFLAGS) $(OPT) -gdwarf-2 -fomit-frame-pointer -Wall
> -Wstrict-prototypes -fverbose-asm -Wa,-ahlms=$(<:.c=.lst) $(DEFS)
> CPPFLAGS = $(MCFLAGS) $(OPT) $(CPPOPT) $(WARN) -Wa,-alms=$(<:.cpp=.lst)
> $(DEFS)
...
> @echo "Compiling C++ $<"
> @$(CPP) -c $(CPPFLAGS) -I . $(INCDIR) $< -o $@
Okay, one last try -- add '-g -gdwarf-2' to the CPPFLAGS? (Leave the
linker as g++ though).
Pete
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
> ASFLAGS = $(MCFLAGS) -g -gdwarf-2 -Wa,-amhls=$(<:.s=.lst) $(ADEFS)
> CPFLAGS = $(MCFLAGS) $(OPT) -gdwarf-2 -fomit-frame-pointer -Wall
> -Wstrict-prototypes -fverbose-asm -Wa,-ahlms=$(<:.c=.lst) $(DEFS)
> CPPFLAGS = $(MCFLAGS) $(OPT) $(CPPOPT) $(WARN) -Wa,-alms=$(<:.cpp=.lst)
> $(DEFS)
...
> @echo "Compiling C++ $<"
> @$(CPP) -c $(CPPFLAGS) -I . $(INCDIR) $< -o $@
Okay, one last try -- add '-g -gdwarf-2' to the CPPFLAGS? (Leave the
linker as g++ though).
Pete
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: C++ debugging with OpenODC and eclipse - marc...@free.fr - Nov 17 9:37:53 2009
Pete, you are my hero! works perfectly, thanks a lot
of course, now if I look to the manual it seems obvious, but some times you don't see the forest because of trees
thanks
Marcel
------------------------------------
______________________________
controlSUITE™ software. Comprehensive. Intuitive. Optimized.
Real-world software for real-time control. Details Here!
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )