Re: SID Faq-O-Matic

Re: SID Faq-O-Matic

[Frank Ch. Eigler]

[-- 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 --]

Re: SID Faq-O-Matic

[Frank Ch. Eigler]

Hi -


On Tue, Apr 15, 2003 at 06:29:57PM -0400, Warhurst Brandon wrote:
> Okay, everything seems to be in place.  I executed your arm-elf-sid command
> and it generated a nice config-file for me (--no-run so I could look at it
> first).  

Excellent - that's a the ideal start.


> However,
> It is trying to load things from library files and the symbols are
> unresolved.  I must have done something wrong at compile time or something to
> create that problem (dlopen can't seem to resolve anything... don't know
> why).  Do I need to run ldd or something like that to refresh my library
> cache?

If you ran "make install", and run sid out of the configure-time-specified
$prefix/bin directory, it should all just work.  There are a ways to work
around problems anyway.  You can set LD_LIBRARY_PATH to $prefix/lib by
hand.  You could configure sid's build tree with "--disable-shared", so no
shared libraries are built or used.


> Secondly, I created two memory sections, but three show up in the config
> file.  And the third one overlaps the first two.  Is that section generated
> for a reason, or can I safely comment it out?

That's exactly the minor complication I was referring to earlier.  The
perl-based front-end doesn't have an option to omit the default memory
region provided for plain process emulation mode.  Until such an option
appears, yes indeed, commenting the unwanted region is the right thing.
(The minimal change may be just to comment out the "connect-bus" directive
that maps the ram/rom component into the address space.)


- FChE