From: "Anthony Tonizzo" <atonizzo@gmail.com>
To: "eCos Disuss" <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: Init sequence for enabling MMU at mpc5xx fails
Date: Tue, 22 Jul 2008 15:54:00 -0000 [thread overview]
Message-ID: <b437ec690807220853w3ed1ffd5he26f728a4472029c@mail.gmail.com> (raw)
Andrey:
The MMU uses burst access to DRAM. It might very well be that
your burst patterns in the UPM memory are not quite correct.
You can check this by setting the BIH bit in the ORx register
for your DRAM. This will inhibit the use of UPM burst patterns and
use single beat patterns instead. If your board now works after
you enable the MMU, then you know where where to look.
Tony
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2008-07-22 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 15:54 Anthony Tonizzo [this message]
2008-07-22 16:06 ` Gary Thomas
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=b437ec690807220853w3ed1ffd5he26f728a4472029c@mail.gmail.com \
--to=atonizzo@gmail.com \
--cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).