From: clark@esteem.com
To: linuxppc-embedded@lists.linuxppc.org
Subject: PPCBoot memory mapping problems
Date: Fri, 18 Aug 2000 17:45:01 -0700 [thread overview]
Message-ID: <1.5.4.32.20000819004501.006984e4@pop.esteem.com> (raw)
Okay here is the situation,
I have hacked & slashed the PPCBoot code to work with our custom
board (all except the flash portion). I have mapped the memory as show below.
address size name BR#/OR# buswidth
0x00000000 8meg Bank0 1 32
0x00800000 8meg Bank1 2 32
0x40000000 2meg Flash0 0 16
0x60000000* 2meg Flash1 3 16
0xFFF00000 whatever IMMR N/A N/A
(* Note will be remapped to the end of flash0 to form contigious flash block
when I get around to hacking the flash code)
I have taken the "include/asm/mbx.h" and replaced its boardinfo
structure with the one I used in the PPCBoot code and then compiled the
kernel. Following the instructions in the readme file, I grabbed
arch/ppc/coffboot/vmlinux.gz and converted as shown. It is given a load
address of 0x00000000 and an entry point 0x0000000C. I put the converted
image into flash using our ICE at address 0x40020000.
Our board boots up checks the kernels CRC then uncompresses it. It
then jumps to 0x0000000C. A little bit later it then jumps to some address
0xC000???? and faults.
Is this what it is supposed to do? Am I supossed to have the RAM
mapped at 0xC0000000? If it loads at address 0 how do I remap it to
0xC0000000 once the kernel starts? Is there any way to force the kernel to
run in lower memory?
Thanks in advance for any help.
Conn Clark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-19 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-19 0:45 clark [this message]
2000-08-19 2:10 ` PPCBoot memory mapping problems Frank Smith
2000-08-19 8:26 ` Wolfgang Denk
2000-08-19 8:26 ` Wolfgang Denk
2000-08-21 11:24 ` Jerry Van Baren
2000-08-21 11:52 ` diekema_jon
2000-08-21 13:25 ` Wolfgang Denk
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=1.5.4.32.20000819004501.006984e4@pop.esteem.com \
--to=clark@esteem.com \
--cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).