From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: chao yu <chaoyu5201314@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: About I-cache and D-cache of MPC8245
Date: Tue, 25 Jan 2005 09:37:37 -0500 [thread overview]
Message-ID: <41F659B1.1040603@smiths-aerospace.com> (raw)
In-Reply-To: <20050125012333.17213.qmail@web90003.mail.scd.yahoo.com>
chao yu wrote:
> Hi, All
> I am a newbie in embeded system from China, recently i enable
> the I-cache and D-cache of MPC8245. But it will crash. What the cause
> might be? I have set the ICE and DCE filed of HID0 reg. and WIMG field
> of BAT reg. Who can give me a hand? Thanks.
>
> Regard,
> Yu.Chao
Your SDRAM initialization is probably not correct. When you turn on
caches, the processor starts doing burst reads of the SDRAM and that is
when SDRAM initialization problems show up.
<http://www.denx.de/twiki/bin/view/DULG/UBootCrashAfterRelocation>
gvb
prev parent reply other threads:[~2005-01-25 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 1:23 About I-cache and D-cache of MPC8245 chao yu
2005-01-25 14:37 ` Jerry Van Baren [this message]
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=41F659B1.1040603@smiths-aerospace.com \
--to=gerald.vanbaren@smiths-aerospace.com \
--cc=chaoyu5201314@yahoo.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).