public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Bart Veer <bartv@redhat.com>
To: james_ch1@sina.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ecos start in ram
Date: Fri, 16 Feb 2001 06:32:00 -0000	[thread overview]
Message-ID: <200102161432.f1GEWNJ04541@sheesh.cambridge.redhat.com> (raw)
In-Reply-To: <000801c097b2$ac8760a0$c408aa0a@inc.inventec>

>>>>> "James" == james chen <james_ch1@sina.com> writes:

    James>         now I am porting eCos to my test board (based
    James> ARM7TDMI), the ROM address is 0x0 and the RAM address is
    James> 0xc000000, but in ecos the RAM address is 0x0, so how to
    James> config memory layout to run Redboot and eCos? I also think
    James> the vectors.S file should be changed, will you tell any?

IIRC on some ARM processors you normally need RAM at location 0x0,
because that is where interrupt vectors etc. are held. You also need
ROM at location 0x0 because bootstraps happen from that address. In
the absence of an MMU, the normal way to resolve this is to have a
memory remap facility: on power up there is ROM at location 0x0, so
bootstrap can proceed; early on during the bootstrap, the remap switch
is toggled and the memory map changes; the ROM moves somewhere else in
memory, and there is now RAM at location 0x0 so that the interrupt
vectors etc. can be updated.

So for a typical eCos application, the RAM might be at 0xC0000000
immediately after power-up but it will be remapped to 0x0 early on.
Hence the eCos memory map will have RAM at 0x0.

The exact details are of course hardware-specific, and will have to be
addressed by your platform port.

Bart

  parent reply	other threads:[~2001-02-16  6:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-15 16:59 james chen
2001-02-15 19:12 ` Gary Thomas
2001-02-15 21:18   ` james chen
2001-02-16  6:32 ` Bart Veer [this message]
2001-02-16  7:48   ` Grant Edwards

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=200102161432.f1GEWNJ04541@sheesh.cambridge.redhat.com \
    --to=bartv@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=james_ch1@sina.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).