public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Warhurst Brandon <Warhurst_Brandon@bah.com>
Cc: sid@sources.redhat.com
Subject: Re: SID Faq-O-Matic
Date: Mon, 14 Apr 2003 14:15:00 -0000	[thread overview]
Message-ID: <20030414101546.A17436@redhat.com> (raw)
In-Reply-To: <3E9ABBE3.6E3A8755@bah.com>; from Warhurst_Brandon@bah.com on Mon, Apr 14, 2003 at 09:47:15AM -0400

[-- Attachment #1: Type: text/plain, Size: 1030 bytes --]

Hi -

On Mon, Apr 14, 2003 at 09:47:15AM -0400, Warhurst Brandon wrote:
> Where would I look if I wanted to make SID support straight binary code
> from actual target hardware (no source/obj/etc... available)?

You probably mean something like having sid run code from, say, an EPROM
image file (oops, dating myself here).  The easiest way to do this is
to get the memory modelling components to load (and optionally save)
their contents from/to an external file.  See "siddoc memory" for the
low-level configuration items that manage this behavior.

The perl-based sid front end (configrun-sid, aka "arm-elf-sid") uses
command line options to specify association with files.  Add a monster
"--memory-region" parameter like:
  % arm-elf-sid --memory-region=0xE000,0x1000,read-only,file=IMAGE ...
It arranges low-level sid configuration bits to load IMAGE into 4096
bytes of simulated memory starting at 0xE000.

Slight complications arise if you need to associate files provided
by default in the various configurations.


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

       reply	other threads:[~2003-04-14 14:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3E9ABBE3.6E3A8755@bah.com>
2003-04-14 14:15 ` Frank Ch. Eigler [this message]
     [not found]   ` <3E9C2C69.792AB080@bah.com>
     [not found]     ` <20030415121223.D6817@redhat.com>
     [not found]       ` <3E9C87E5.6D8FBBD7@bah.com>
2003-04-15 23:58         ` Frank Ch. Eigler

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=20030414101546.A17436@redhat.com \
    --to=fche@redhat.com \
    --cc=Warhurst_Brandon@bah.com \
    --cc=sid@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).