From: "Dave Airlie" <airlied@parthus.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] eCos PID ROM/RAM
Date: Sat, 27 Jan 2001 04:47:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0101271243430.16685-100000@platinum.limerick.sslinc.com> (raw)
I created a ROMRAM config for my PID which copies my ROM image down to RAM
and jumps to it ... it does the copy in PLATFORM_SETUP1 Macro, after
enabling the RAM, I've also used the PID RAM linker files for the ROMRAM
setup and added defined(ROMRAM) where I thought was necessary, however
I've hit a problem with the booting of the ROM, because I've used RAM
linked scripts (which is correct because it is running out of RAM), the
reset_vector is incorrect it is at 0x8044, so I am hexediting the produced
image to make the reset_vector 0x04000044, where the ROM is,
How to other platforms handle this problem? or do they do some MMU pokery
to get around it? also I have a ldr pc,0x8074 in my code to jump to RAM,
this is something I don't like anyone got a better way for me to jump to
the RAM image once it is copied?
I'll submit the patches back if I get them cleaned up a bit... (they
should be small enough to not need copyright assignment, and most of the
code is RH's anyways :-)
dave.
--
David Airlie, Software Engineer, Parthus Technologies plc.,
Mary Rosse Centre, National Tech Park, Limerick, Ireland.
t: +353-61-508116 / f: +353-61-508101 / David.Airlie@parthus.com
next reply other threads:[~2001-01-27 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 4:47 Dave Airlie [this message]
2001-01-29 10:01 ` Jonathan Larmour
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=Pine.LNX.4.21.0101271243430.16685-100000@platinum.limerick.sslinc.com \
--to=airlied@parthus.com \
--cc=ecos-discuss@sources.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).