From: Paul White <pwhite@networkrobots.com>
To: Freddy Lugo <wilflugo@yahoo.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Can not access memory after turning MMU on
Date: Mon, 07 May 2001 13:56:08 -0700 [thread overview]
Message-ID: <200105072049.f47Knh628959@stimpy.networkrobots.com> (raw)
In-Reply-To: <20010507204100.56613.qmail@web9901.mail.yahoo.com>
Hi Freddy,
What address is it trying to address next? It needs to be sure its in the
range of the BATS setup by initial_bats, which maps the first 16Meg of
memory to KERNELBASE.
After turning MMU on, it should finish relocating the kernel. Is this the
part thats failing?
I'm referencing arch/ppc/kernel/head.S above.
Paul W.
At 01:41 PM 5/7/2001 -0700, Freddy Lugo wrote:
>
>Hi,
>
>After turning the MMU (turn_on_mmu) the next memory
>access instruction (stwu) can not be translated, the
>memory can not be accessed and the system halt. I
>check the list archives and there are references to
>set the Debug Enable Register (DER) to an
>"appropriate" value. I am working with the MPC750 and
>in the Users Manual I can't find any reference to such
>register. Also I checked my bdi2000 (in case it was a
>register on the bdi) and I didn't found anything.
>
>This register exists or has its counterpart on the
>MPC750? Besides the DER value, there are other
>methods to work and find the problem?
>
>Thanks,
>
>Freddy Lugo
>
>
-------------------------------------------------------------
Network Robots, Inc. /--\ Paul H. White
/ ____ \
4695 Chabot Dr. #200 / ( oo ) \ Software Developer
Pleasanton, CA 94588 / ---- \ Engineering
(925) 924-8600 \ ---- / (925) 580-4883
\ V--V /
\ /
\--/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-07 20:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 20:41 Can not access memory after turning MMU on Freddy Lugo
2001-05-07 20:56 ` Paul White [this message]
2001-05-07 22:00 ` Dan Malek
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=200105072049.f47Knh628959@stimpy.networkrobots.com \
--to=pwhite@networkrobots.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wilflugo@yahoo.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 NNTP newsgroup(s).