linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Lei Sun" <leisun124@gmail.com>
Cc: Dave Liu <r63238@freescale.com>, linuxppc-embedded@ozlabs.org
Subject: Re: memory corruption after MMU turned on
Date: Sun, 19 Nov 2006 01:48:01 +0100	[thread overview]
Message-ID: <20061119004801.A57B3353B9C@atlas.denx.de> (raw)
In-Reply-To: Your message of "Sat, 18 Nov 2006 16:53:02 EST." <f9a7e7a80611181353p21dce384m21f30bc9d8935a8d@mail.gmail.com>

In message <f9a7e7a80611181353p21dce384m21f30bc9d8935a8d@mail.gmail.com> you wrote:
> I tried enable i-cache, but it looks fine, however if i enable
> d-cache, u-boot corrupted right away, debugger showed some garbage
> memory instead of valid instruction.

Did you read the U-Boot README? It explains why this cannot work.

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

Did you read the FAQ, like
http://www.ultsol.com/faq_p305.htm ?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
"Everything should be made as simple as possible, but not simpler."
                                                    - Albert Einstein

  reply	other threads:[~2006-11-19  0: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
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 [this message]
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=20061119004801.A57B3353B9C@atlas.denx.de \
    --to=wd@denx.de \
    --cc=leisun124@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=r63238@freescale.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).