From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28087 invoked by alias); 14 Apr 2003 14:15:55 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 27915 invoked from network); 14 Apr 2003 14:15:49 -0000 Received: from unknown (HELO touchme.toronto.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 14 Apr 2003 14:15:49 -0000 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id C89BF800087; Mon, 14 Apr 2003 10:15:48 -0400 (EDT) Received: from toenail.toronto.redhat.com (IDENT:fche@localhost [127.0.0.1]) by toenail.toronto.redhat.com (8.11.6/8.11.6) with ESMTP id h3EEFmk17516; Mon, 14 Apr 2003 10:15:48 -0400 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.12.8/8.12.8/Submit) id h3EEFl3g017512; Mon, 14 Apr 2003 10:15:47 -0400 Date: Mon, 14 Apr 2003 14:15:00 -0000 From: "Frank Ch. Eigler" To: Warhurst Brandon Cc: sid@sources.redhat.com Subject: Re: SID Faq-O-Matic Message-ID: <20030414101546.A17436@redhat.com> References: <3E9ABBE3.6E3A8755@bah.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3E9ABBE3.6E3A8755@bah.com>; from Warhurst_Brandon@bah.com on Mon, Apr 14, 2003 at 09:47:15AM -0400 X-SW-Source: 2003-q2/txt/msg00006.txt.bz2 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 1030 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 --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+msKSVZbdDOm/ZT0RAqH9AJsGTDFz8A1GVAZubSXyA+aUkuEZywCdEDSi onZQXPJePN3z4oHC48lVTsE= =/NFM -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH--