public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dave Littell <littelld@verizon.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] AMCC PPC440EPx/sequoia stability question...
Date: Wed, 23 Apr 2008 21:17:32 -0500	[thread overview]
Message-ID: <480FEDBC.2010401@verizon.net> (raw)
In-Reply-To: <200804231449.24746.sr@denx.de>

Stefan Roese wrote:
> On Wednesday 23 April 2008, Dave Littell wrote:
>> I'm working on an AMCC PPC440EPx-based platform that's similar to the
>> Sequoia.  The board runs pretty well, but occasionally takes exceptions
>> both in U-Boot and while running Linux.  The exceptions vary from
>> Illegal Instructions to FP Unavailable to FP Unimplemented to ITLB and
>> DTLB Errors, to DSI, etc., which made us believe there's a problem with
>> SDRAM.
> 
> Yes, this is my first idea too. Almost every time such "random" errors are 
> seen, SDRAM setup/initialization is the cause for it.
> 
>> Sometimes there are simple hard lockups from which even the JTAG 
>> can't regain control.  However, the SDRAM physical/electrical and DDR
>> Controller configurations have been investigated in detail (and some
>> corrections made) with no resulting improvement in the exception behavior.
> 
> Is the SDRAM termination similar to the one used on Sequoia too? Are you using 
> soldered chips and not DIMM modules? Is ECC available?
> 

Termination: very likely - they stayed very close to Sequoia, but I'll ask.

We're using soldered chips and there's no ECC.

>> We see problems primarily at 667 MHz but have noted some issues at 533
>> MHz as well.  Some boards seem particularly susceptible to this while
>> others rarely (if ever) exhibit the problem.
>>
>> At this point all possibilities are on the table and I'm looking for any
>> input from anyone with experience (good, bad, or whatever) with this
>> processor and/or designs similar to the Sequoia.
> 
> If you scan the U-Boot mailing list for 440EPx/Denali DDR2 problems, you will 
> most likely find some references.
> 

Will do, thanks for the pointer.

> Please note that I recently introduced a CFG_MEM_TOP_HIDE option for the 
> 440EPx CHIP 11 errata. I suggest you take a look at this too and see if this 
> changes your behavior.
> 

I remember this - PPC440EPx Revision A errata CHIP_11, right?


Thanks,
Dave

  parent reply	other threads:[~2008-04-24  2:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23  3:33 [U-Boot-Users] AMCC PPC440EPx/sequoia stability question Dave Littell
2008-04-23 12:49 ` Stefan Roese
2008-04-24  1:10   ` Josh Boyer
2008-04-24  4:36     ` Stefan Roese
2008-04-24 12:00       ` Josh Boyer
2008-04-24 13:06         ` Stefan Roese
2008-04-24  2:17   ` Dave Littell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-04-23 14:10 Mike Nuss
2008-04-24 15:59 Niklaus Giger

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=480FEDBC.2010401@verizon.net \
    --to=littelld@verizon.net \
    --cc=u-boot@lists.denx.de \
    /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