linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: clark@esteem.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: PPCBoot memory mapping problems
Date: Sat, 19 Aug 2000 10:26:22 +0200	[thread overview]
Message-ID: <200008190826.KAA17158@denx.local.net> (raw)
In-Reply-To: Your message of "Fri, 18 Aug 2000 17:45:01 PDT." <1.5.4.32.20000819004501.006984e4@pop.esteem.com>


Hi,

in message <1.5.4.32.20000819004501.006984e4@pop.esteem.com> you wrote:
>
>         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.

Looks OK.

> 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

Be careful here! This depends on the kernel version! Entry point  0xC
is/was  used in "older" kernel versions like 2.2.13. This has changed
in 2.3.x kernels, which started executing code form 0, so if you  are
running a 2.3 / 2.4 kernel make sure to set the entry point to 0x0.

>         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

This is OK - as soon as the kernel switches on the MMU  it  will  use
virtual addresses.

> 0xC000???? and faults.

This may be casued by a bad entry point (see above), or you might  be
fooled  if  you're  running  with  an ICE that does not work with MMU
(make sure to set the DER to a sensible value, or use a better ICE).

>         Is this what it is supposed to do? Am I supossed to have the RAM

The use of 0xC00xxxxx addresses is supposed to happen, the faults are
not supposed to happen - if they really are. I guess it's  just  your
ICE...

> 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?

You don't remap the  RAM;  the  kernel  will  take  care  of  address
translation of virtual to physical addresses.


Note 1: I'm not sure if too  many  people  on  the  linuxppc-embedded
        mailing   list   are   interested   in  PPCBoot  issues;  the
        ppcboot-users mailing list is  probably  a  more  appropriate
        place for such discussion.

Note 2: Although not yet officially announced, ppcboot-0.4.3  is  out
        (both   on   the   CVS   server   and   on   our  FTP  server
        (ftp://ftp.demx.de/pub/ppcboot/ppcboot-0.4.3.tar.gz); on  the
        CVS  server  there are even some more recent modifications in
        preparation of suport for some IBM 4xx based board.

Hope this helps,

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
I have a theory that it's impossible to prove anything, but  I  can't
prove it.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-08-19  8:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-19  0:45 PPCBoot memory mapping problems clark
2000-08-19  2:10 ` Frank Smith
2000-08-19  8:26   ` Wolfgang Denk
2000-08-19  8:26 ` Wolfgang Denk [this message]
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=200008190826.KAA17158@denx.local.net \
    --to=wd@denx.de \
    --cc=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).