From: Andrew Lunn <andrew@lunn.ch>
To: J?r?my Alles <jeremy.alles@orange-ftgroup.com>
Cc: 'eCos Discussion' <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Configuring an eCos application to debug it using GDB
Date: Thu, 27 Mar 2008 09:02:00 -0000 [thread overview]
Message-ID: <20080327084523.GL16575@lunn.ch> (raw)
In-Reply-To: <200803270827.m2R8Rp2U005231@smtp.silicomp.fr>
On Thu, Mar 27, 2008 at 09:27:50AM +0100, J?r?my Alles wrote:
> Hi,
>
> I'm trying to configure properly my eCos application in order to
> debug it using GDB (over Ethernet). I'm using an AT91 based development kit
> with Redboot already flashed on it (by someone else in my company).
Do you have the configuration that was used to build this redboot
image?
> The problem is I think that I'm missing something in my
> configuration (ecos.ecc), as when my application starts, it returns 54321
> and not something like $O3534313231#56+. That is why I think i'm doing
> something wrong.
This is to do with gdb mangling. Normally it should work out if it
needs to mangle nor not, depending on if gdb is connected or not.
Take a look at CYGSEM_HAL_DIAG_MANGLER.
What i don't know is if redboot or the application does the mangling.
I think it is redboot, but maybe Gary can confirm this.
Note, this only applies to output from diag_printf. If you open the
serial port, /dev/ser0, and write to that, no mangling is performed.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2008-03-27 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 8:45 Jérémy Alles
2008-03-27 9:02 ` Andrew Lunn [this message]
2008-03-27 14:02 ` Gary Thomas
2008-03-27 14:55 ` Jérémy Alles
2008-03-27 15:27 ` Gary Thomas
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=20080327084523.GL16575@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=jeremy.alles@orange-ftgroup.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).