From: "james chen" <james_ch1@sina.com>
To: "Gary Thomas" <gthomas@cambridge.redhat.com>
Cc: <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] ecos start in ram
Date: Thu, 15 Feb 2001 21:18:00 -0000 [thread overview]
Message-ID: <000701c097d7$c429a400$c408aa0a@inc.inventec> (raw)
In-Reply-To: <XFMail.20010215201151.gthomas@cambridge.redhat.com>
my test board have no MMU, will you give suggestions?
>
> On 16-Feb-2001 james chen wrote:
> > Hello,
> >
> > now I am porting eCos to my test board (based ARM7TDMI), the ROM
> > address is 0x0 and the
> > RAM address is 0xc000000, but in ecos the RAM address is 0x0, so how to
> > config memory layout to run Redboot and eCos? I also think the vectors.S
> > file should be changed, will you tell any?
>
> This sounds very much like the Assabet (SA1110) system. We use the MMU
> to remap memory, swapping the RAM and ROM addresses around.
>
>
next prev parent reply other threads:[~2001-02-15 21:18 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 [this message]
2001-02-16 6:32 ` Bart Veer
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='000701c097d7$c429a400$c408aa0a@inc.inventec' \
--to=james_ch1@sina.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=gthomas@cambridge.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).