From: fche@redhat.com (Frank Ch. Eigler)
To: "Paul Pham" <ppham@MIT.EDU>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] GDB simulator target?
Date: Fri, 02 Feb 2001 10:59:00 -0000 [thread overview]
Message-ID: <o5y9voewsk.fsf@toenail.toronto.redhat.com> (raw)
In-Reply-To: <ELEIIPIOKOBPDLLMNHKJOEGACBAA.ppham@mit.edu>
"Paul Pham" <ppham@MIT.EDU> writes:
: How useful is the GDB simulator target? [...]
: For example, if a printf requires outputting data to the UART, will the
: simulator know which registers to write to? [...]
Few of the gdb simulators are capable of running eCos software. The
arm one in particular lacks models for several peripherals that eCos
needs. In contrast, the arm simulator that comes with our recently
released sid simulator does have more peripherals.
One of the aims of the sid project is to provide an increasing library
of simulation models, suitable for debugging operating systems such as
eCos and that run on them.
See < http://sources.redhat.com/sid >.
- FChE
prev parent reply other threads:[~2001-02-02 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 14:58 Paul Pham
2001-02-02 10:59 ` Frank Ch. Eigler [this message]
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=o5y9voewsk.fsf@toenail.toronto.redhat.com \
--to=fche@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=ppham@MIT.EDU \
/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).