From: Dave Liu <r63238@freescale.com>
To: Lei Sun <leisun124@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: memory corruption after MMU turned on
Date: Fri, 17 Nov 2006 16:48:44 +0800 [thread overview]
Message-ID: <1163753324.3655.18.camel@localhost.localdomain> (raw)
In-Reply-To: <f9a7e7a80611160744t7071ff6clf5e1d42cfaa2c856@mail.gmail.com>
On Thu, 2006-11-16 at 10:44 -0500, Lei Sun wrote:
> Hi all:
> I am trying to bring up customized board based on MPC8270, the
> kernel version is 2.4.30, it works fine on one of the Eval board
> (PQ2FADS-VR, which use MPC8275).
> The kernel hangs after uncompressing is done, further debug shows
> that it hangs right after "rfi " instruction of the turn_on_mmu:
> function in head.S
>
> turn_on_mmu:
> 240 mfmsr r0
> 241 ori r0,r0,MSR_DR|MSR_IR
> 242 mtspr SRR1,r0
> 243 lis r0,start_here@h
> 244 ori r0,r0,start_here@l
> 245 mtspr SRR0,r0
> 246 SYNC
> 247 RFI /* enables MMU */
>
> After i step over the RFI instruction, the PC points to C000XXX , but
> all memory content is 0 by then.
> my BATU0 is 0xC000FFE0 BATL0 is 0x00000002, I have 128MB RAM. The
> u-boot works fine, without MMU turned on. We do have some hardware
> problem, such that i have to lower the bus frequency to make the SDRAM
> stable. What physical parameter could cause the board not working with
> MMU on?
When MMU turn on, the kernel memory should be cacheable, so the
processor will burst read instructions from memory to i-cache. Did you
do the burst read/write memory test in u-boot? As you said, you did not
do the test.
-Dave
next prev parent reply other threads:[~2006-11-17 8:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 15:44 memory corruption after MMU turned on Lei Sun
[not found] ` <1628E43D99629C46988BE46087A3FBB97AFFDC@ep-01.EmbeddedPlanet.local>
2006-11-16 16:42 ` Lei Sun
2006-11-17 8:48 ` Dave Liu [this message]
2006-11-17 16:47 ` Lei Sun
2006-11-18 10:03 ` Dave Liu
2006-11-18 21:53 ` Lei Sun
2006-11-19 0:48 ` Wolfgang Denk
2006-11-19 6:01 ` Dave Liu
-- strict thread matches above, loose matches on Subject: below --
2006-11-16 16:11 Claus Gindhart
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=1163753324.3655.18.camel@localhost.localdomain \
--to=r63238@freescale.com \
--cc=leisun124@gmail.com \
--cc=linuxppc-embedded@ozlabs.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).