public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Matt Sartori" <msartori@hanoverdisplays.com>
To: "Andrew Lunn" <andrew@lunn.ch>
Cc: "eCos Discussion" <ecos-discuss@ecos.sourceware.org>
Subject: RE: [ECOS] Simple Redboot Q's
Date: Tue, 26 Jul 2005 17:03:00 -0000	[thread overview]
Message-ID: <F9885E669725F248A1F6DB9109FDD679357122@Molly.hanover.local> (raw)

Yes, that all the jumps and references within the code are relative, not
absolute.
I think what I'm not quite understanding is what the load does. 
I would expect the loading of an elf to involve the interpretation of
the file as to where to put it (and probably other stuff), however
loading an elf explicitly to a location (with -b) doesn't make logical
sense to me since the elf already knows where it wants to go. 
Equally baffling to me is when I load a .bin to an explicit location
then I can't just run it from that location.
Only when I load the .bin into the same memory location as what I've put
in the binary's linker script does it work (yes, I've finally managed to
get it to run my code :) even if not quite sure why).

I apologize if this is basic stuff.

m@

-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch] 
Sent: 26 July 2005 17:30
To: Matt Sartori
Cc: eCos Discussion
Subject: Re: [ECOS] Simple Redboot Q's


> >Unless your code is position independent (or very smart), this is 
> >most
> certainly your problem.
> 
> Ok, good. That's something I can look at then.
> Redboot, despite being a ROM build, says it's using RAM from
0x20000000
> to 0x20005b68, so I've made
> my linker script place CODE at 0x20005b68 and DATA at 0x20008000 (with
a
> total RAM range of 0x10000).
> This, I take it, is only significant if I load it as an elf. And,
again
> if I understand correctly, when loaded as -r it just goes where I put
> it.
> Obviously there's still something I don't understand correctly 'cause
it
> doesn't work. 

Find out what position independant means. The comments above make me
think you understand what this means.

        Andrew

--------------------------------------------------------------------------------


The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.

If you received this in error, please contact the sender or postmaster (postmaster@hanoverdisplays.com) and delete the material from any computer.

Although we routinely screen for viruses, addressees should check this e-mail and any attachment for viruses. We make no warranty as to absence of viruses in this e-mail or any attachments.

Our Company's email policy is to permit incidental personal use. If this email is of a personal nature, it must not be relied upon as expressing the views or opinions of the company.

Visit out website at www.hanoverdisplays.com



--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2005-07-26 17:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-26 17:03 Matt Sartori [this message]
2005-07-26 17:21 ` Andrew Lunn
  -- strict thread matches above, loose matches on Subject: below --
2005-07-27 11:17 Matt Sartori
2005-07-26 15:55 Matt Sartori
2005-07-26 16:30 ` Andrew Lunn
2005-07-26 14:52 Matt Sartori
2005-07-26 14:59 ` Gary Thomas
2005-07-26 13:20 Matt Sartori
2005-07-26 13:28 ` Andrew Lunn
2005-07-26 13:28 ` Gary Thomas
2005-07-26 10:16 Matt Sartori
2005-07-26 11:05 ` Andrew Lunn
2005-07-26 13:08   ` Gary Thomas

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=F9885E669725F248A1F6DB9109FDD679357122@Molly.hanover.local \
    --to=msartori@hanoverdisplays.com \
    --cc=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).