[ECOS] several remote gdb questions/problems

[ECOS] several remote gdb questions/problems

[Neundorf, Alexander]

Hi,

I'm using ecos cvs on an XScale.
Basically debugging with arm-elf-gdb/insight works.
It's gcc 3.2.1 and gdb 6.1

Two (maybe three) issues:
It seems I am not able to pause a running program.
ecos/packages/hal/arm/xscale/pxa2x0/hal_diag.c contains code which seems to check for ctrl-c  . But pressing ctrl-c in arm-elf-gdb doesn't break the program :-/
Redboot is configured as rom-monitor, with gdb_break_support (not ctrl-c support), since the stubs are present in redboot.
The app is configured without stubs, and checking gdb_break_support or ctrlc_support doesn't change the behaviour.
Any hints why it doesn't work or how to find out the reason ?

Next one: I know this question was posted here several times already, but I didn't find a definitive answer. I have (only) one serial port, which I use for diag_printf(). On the xscale I read characters from /dev/ttydiag and interpret the commands.
gdb runs over the same serial line.
Is it possible to use gdb and at the same time see the diag_printf() output and be able to enter some commands via the serial line so that they reach my interpreter on the xscale ?

(third one: are there known problems with adding global object instances to the watch window with insight 6.1 ? When I try this, insight stalls and I have to kill it).

Thanks for any pointers
Alex



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] several remote gdb questions/problems

[Øyvind Harboe]

> Hi,
> 
> I'm using ecos cvs on an XScale.
> Basically debugging with arm-elf-gdb/insight works.
> It's gcc 3.2.1 and gdb 6.1
> 
> Two (maybe three) issues:
> It seems I am not able to pause a running program.
> ecos/packages/hal/arm/xscale/pxa2x0/hal_diag.c contains code which seems to check for ctrl-c  . But pressing ctrl-c in arm-elf-gdb doesn't break the program :-/
> Redboot is configured as rom-monitor, with gdb_break_support (not ctrl-c support), since the stubs are present in redboot.
> The app is configured without stubs, and checking gdb_break_support or ctrlc_support doesn't change the behaviour.
> Any hints why it doesn't work or how to find out the reason ?
> 
> Next one: I know this question was posted here several times already, but I didn't find a definitive answer. I have (only) one serial port, which I use for diag_printf(). On the xscale I read characters from /dev/ttydiag and interpret the commands.
> gdb runs over the same serial line.
> Is it possible to use gdb and at the same time see the diag_printf() output and be able to enter some commands via the serial line so that they reach my interpreter on the xscale ?
> 
> (third one: are there known problems with adding global object instances to the watch window with insight 6.1 ? When I try this, insight stalls and I have to kill it).
> 
> Thanks for any pointers

Have you considered a hardware JTAG debugger? 

For almost any non-trivial project it will be a major timesaver.

I'm using the BDI2000 which also acts as a flash programmer.

> Alex

-- 
Øyvind Harboe
http://www.zylin.com



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss