linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jan Damborsky <Jan.Damborsky@devcom.cz>
To: "Wells, Charles" <Charles.Wells@NielsenMedia.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problem with data cache on MPC823E
Date: Mon, 27 Jan 2003 08:42:06 +0100	[thread overview]
Message-ID: <3E34E2CE.3040102@devcom.cz> (raw)
In-Reply-To: DF2B720CF774D21189EE00805FA7FA220517835A@nmrusdunsx3.nielsenmedia.com


Wells, Charles wrote:

>Jan,
>
>While reviewing your original email, I noticed the following statement.
>
>
>
>>May be it is because we have floating BI (burst inhibit) CPU singnal.
>>
>>
>
>My MPC823UM manual (Rev 1, p. 13-36, section 13.4.9.2 BURST INHIBIT SIGNAL)
>states the following:
>
>    "This signal must be pulled up to Vdd with a pullup resistor."
>
>This is shown in figure 13-24.  Have you tried adding a pullup resistor?
>
I think it is the reason, why our board behaves so erraticaly (we have
developed our board with
MPC823UM Revision 0, there is only "should be pulled up", but in
Revision 1 is "must be pulled up",
so we have to base our next development on newest documentation - like
it "must be" always).
Because when I set BIH bit in OR register, there are no problems. I
think because there are no bursts.
But solution of this problem is not so trivial. Because MPC823 is in BGA
package and BI signal
is unconnected, the appropriate pin is unreachable. So I am not sure we
will be successful
in connecting BI to pullup, may be we will be forced to create new PCB,
but it is future.

>Also, where did you get your UPM table for DRAM?

We have derived UPM settings from Motorola MPC823ADS documentation,
and verified them in Motorola graphical software for UPM settings
visualisation, so I think it is OK.

                                                                Thank
you for your help very much,

                Jan Damborsky


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2003-01-27  7:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DF2B720CF774D21189EE00805FA7FA220517835A@nmrusdunsx3.nielsenmedia.com>
2003-01-27  7:42 ` Jan Damborsky [this message]
2003-01-27 12:18 ` Problem with data cache on MPC823E - now solved Jan Damborsky
2003-01-21 20:40 Problem with data cache on MPC823E Wells, Charles
2003-01-22  9:02 ` Jan Damborsky
  -- strict thread matches above, loose matches on Subject: below --
2003-01-21 16:28 Jan Damborsky
2003-01-21 19:49 ` Wolfgang Denk
2003-01-22  9:05   ` Jan Damborsky

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=3E34E2CE.3040102@devcom.cz \
    --to=jan.damborsky@devcom.cz \
    --cc=Charles.Wells@NielsenMedia.com \
    --cc=linuxppc-embedded@lists.linuxppc.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).