public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Neundorf, Alexander" <Alexander.Neundorf@jenoptik.com>
To: <ecos-discuss@sources.redhat.com>
Subject: AW: [ECOS] several remote gdb questions/problems
Date: Tue, 10 Aug 2004 06:11:00 -0000	[thread overview]
Message-ID: <5A8A17126B73AC4C83968F6C4505E3C5EFB6CA@JO-EX01.JENOPTIK.NET> (raw)

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

             reply	other threads:[~2004-08-10  6:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  6:11 Neundorf, Alexander [this message]
2004-08-10  8:21 Neundorf, Alexander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5A8A17126B73AC4C83968F6C4505E3C5EFB6CA@JO-EX01.JENOPTIK.NET \
    --to=alexander.neundorf@jenoptik.com \
    --cc=ecos-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).