linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Eric N. Johnson (ACD)" <ejohnson@acdstar.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: MPC5200 Rev. B
Date: Mon, 11 Jul 2005 11:43:36 -0500	[thread overview]
Message-ID: <6.2.3.4.1.20050711112652.02b82cc8@mail.int.acdstar.com> (raw)
In-Reply-To: <20050711113948.vznzvgxu15nkkwcg@webmail.ellipticity.com>

mgberry@ellipticity.com wrote:
>Has anyone experienced any issues with the Rev. B silicon for the 
>MPC5200.  We are seeing Linux hanging and are suspecting the SDRAM 
>errata for Rev. B.  If we disable the cache this seems to improve 
>but will still crash over time in heavy loads.  We have not seen any 
>of these type issues with the original rev.

Are you sure you have revision B of the MPC5200?  Freescale has 
announced a "B" version, but I don't believe that any of them have 
hit the public yet.  There may be some engineering grade samples out 
there. (Let me know if you really do have "B" parts.  Freescale has 
been telling me "real soon now" since last year)

More likely you're seeing the "B" in the part number, as in 
MPC5200CBV400.  The chip revision is the "mask set" on the next line 
of printing.  The latest public version I know of is L25R.

The L25R version has a major bug that you basically can't use two CS 
pins for SDRAM, and the DDR implimentation is borderline at best.

Exactly what problems are seeing?  What hardware platform do you run 
on?  We're using an MPC5200 with SDR-SDRAM running at 132MHz (two 16 
bit SDRAM devices), and haven't seen any issues.

I don't know what bootloader you're using, but I believe uboot has 
basic memory testing built in.  This would allow you to isolate 
memory issues from software issues.

Eric

------------------------------------
Eric Johnson, Electrical Engineer
Advanced Communication Design
   7901 12th Avenue South
   Bloomington, MN 55425
Ph: 952-854-4000  Fax: 952-854-5774

  reply	other threads:[~2005-07-11 16:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-11 15:39 MPC5200 Rev. B mgberry
2005-07-11 16:43 ` Eric N. Johnson (ACD) [this message]
2005-07-11 17:41   ` Nick Barendt
2005-07-11 19:46     ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2005-07-11 18:13 mgberry
2005-07-12 13:25 Matt_Berry
2005-07-12 20:37 ` Wolfgang Denk
2005-07-13 14:30 Matt_Berry

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=6.2.3.4.1.20050711112652.02b82cc8@mail.int.acdstar.com \
    --to=ejohnson@acdstar.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).