AW: [ECOS] several remote gdb questions/problems

AW: [ECOS] several remote gdb questions/problems

[Neundorf, Alexander]

...
> Ok, I opened /dev/ttydiag in my app and this seems to have 
> the effect that the break events don't get through. So I 
> added manually the check for ctrl-c (0x03) when reading from 
> /dev/ttydiag and call cyg_hal_user_break() when this happens. 
> Seems to work perfectly :-)

More important: both "Work with ROM monitor" and "Inherit console settings from ROM monitor" must be enabled with configtool for the application.
  
> Adding a "write-only" mode to cutecom (http://cutecom.sf.net) 
> solved the problem for me :-). Now I can debug with gdb and 
> enter commands through cutecom.

Ok, next version of cutecom (0.10.1) will work correctly, in 0.10.0 there is a bug with this feature.

Bye
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

AW: [ECOS] several remote gdb questions/problems

[Neundorf, Alexander]

Hi,

maybe some people are interested or have the same issues, so I post my findings here so that they end up in the archives:

> 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 ?

Ok, I opened /dev/ttydiag in my app and this seems to have the effect that the break events don't get through. So I added manually the check for ctrl-c (0x03) when reading from /dev/ttydiag and call cyg_hal_user_break() when this happens. Seems to work perfectly :-)
 
> 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 ?

Adding a "write-only" mode to cutecom (http://cutecom.sf.net) solved the problem for me :-). Now I can debug with gdb and enter commands through cutecom.
Isn't there a way to send commands directly thgough gdb to the device ?
 
> (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).

Well, the object was too big (several megabytes, I should have thought about this before), it works with smaller objects.
 
Bye
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