public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: sebastien.andre@sxb.bsf.alcatel.fr
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] GDB and eCos
Date: Wed, 13 Jun 2001 04:19:00 -0000	[thread overview]
Message-ID: <200106131119.f5DBJfS19861@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <3B272602.6A05CE57@sxb.bsf.alcatel.fr>

>>>>> "Sebastien" == andre33  <sebastien.andre@sxb.bsf.alcatel.fr> writes:

    Sebastien>     Hello,
    Sebastien>     So i'm a newbie

    Sebastien>     It seem that GDB can emulate the target !! i'm
    Sebastien>     wrong ?

Partly correct.

Typically when gcc is ported to a new architecture, one of the first
steps is to write an instruction set simulator for that architecture.
This allows the compiler folks to do their development and testing
before any hardware exists. It is also very useful for subsequent
maintenance. However, this is just an instruction set simulator. It
will do enough to support compiler testing. It will provide only
minimal I/O facilities which bear no resemblance to how I/O happens on
real hardware. Hence typically it cannot be used for eCos development.
The simulator gets built into gdb when you configure for the
appropriate target.

During the early days of eCos development, the simulators for two of
the initial targets (AM31 and TX39) were enhanced to support
architectural simulation of specific boards, the stdeval1 board and
the JMR-TX3904 board. This architectural simulation included support
for a system clock, serial I/O, and interrupt handling, but not for
anything more advanced like ethernet or PCI. In addition eCos was
ported to the PowerPC psim simulator. More details of these can be
found at http://sources.redhat.com/ecos/hardware.html and in the
Getting Started guides for those targets.

More recent work on architectural simulators within Red Hat has
happened in the context of the SID project, http://sources.redhat.com/sid/
Unfortunately I do not really have time to track that project closely
but I suggest you take a look through their web pages and
documentation.

Bart

  reply	other threads:[~2001-06-13  4:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13  1:36 andre33
2001-06-13  4:19 ` Bart Veer [this message]
2001-06-13  4:46   ` andre33
2001-06-13  7:44     ` [ECOS] cyg_semaphore_post Joerg Rapka
2001-06-13  8:27       ` Bart Veer

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=200106131119.f5DBJfS19861@sheesh.cambridge.redhat.com \
    --to=bartv@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=sebastien.andre@sxb.bsf.alcatel.fr \
    /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).