From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] amcc kilauea odd crashes
Date: Thu, 23 Oct 2008 13:30:08 +0200 [thread overview]
Message-ID: <200810231330.08865.sr@denx.de> (raw)
In-Reply-To: <20081023112049.8AAF7810ED3B@gemini.denx.de>
Hi Wolfgang,
On Thursday 23 October 2008, Wolfgang Denk wrote:
> > > Should we not backout the autocalib patches that cause the problem
> > > until a stable working solution is found?
> >
> > Not sure. My hope is that AMCC find a solution quickly. They should
> > receive the failing board this week.
> >
> > And they already did send a "fix" (more a workaround) for this problem:
> >
> > [PATCH v2] ppc4xx: Fix DDR2 auto calibration on Kilauea 600MHz
> >
> > which you rejected. So I suggest to wait for a few days.
>
> Well, that was one full month ago, and nothing happened since.1s
That's not correct. One patch got checked in which definitely made the
situation better:
f8a00dea841d5d75de1f8e8107e90ee1beeddf5f
ppc4xx: Reset and relock memory DLL after SDRAM_CLKTR change
After changing SDRAM_CLKTR phase value rerun the memory preload
initialization sequence (INITPLR) to reset and relock the memory
DLL. Changing the SDRAM_CLKTR memory clock phase coarse timing
adjustment effects the phase relationship of the internal, to the
PPC chip, and external, to the PPC chip, versions of MEMCLK_OUT.
Signed-off-by: Adam Graham <agraham@amcc.com>
Signed-off-by: Victor Gallardo <vgallardo@amcc.com>
Signed-off-by: Stefan Roese <sr@denx.de>
Unfortunately it didn't fix all problems. AMCC already provided another patch
for testing purposes. Not to the list but to me (and you) directly. Please
find it attached again. Would be great if Markus could test it on the failing
Kilauea.
> I see people running into problems with the current code, so I vote
> to back out the culprit until a real fix has been found.
Hmmm, "people" have been running into this problem before too. That we me.
Again, let's please wait at least for Adam and/or Victor to comment on this
issue. It should only be a few hours until they read their mails.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
-------------- next part --------------
An embedded message was scrubbed...
From: Adam Graham <agraham@amcc.com>
Subject: [PATCH 1/1] Check for memory rank missed oversample during DDR autocalibration.
Date: Tue, 14 Oct 2008 19:24:13 -0700
Size: 4264
Url: http://lists.denx.de/pipermail/u-boot/attachments/20081023/c6bd7b79/attachment.eml
next prev parent reply other threads:[~2008-10-23 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 10:20 [U-Boot] amcc kilauea odd crashes Markus Klotzbücher
2008-10-23 10:51 ` Stefan Roese
2008-10-23 11:04 ` Wolfgang Denk
2008-10-23 11:15 ` Stefan Roese
2008-10-23 11:20 ` Wolfgang Denk
2008-10-23 11:30 ` Stefan Roese [this message]
2008-10-23 12:37 ` Markus Klotzbücher
2008-10-23 12:52 ` Stefan Roese
2008-10-24 1:54 ` Adam Graham
2008-10-24 6:59 ` Stefan Roese
2008-10-23 14:51 ` prodyut hazarika
2008-10-23 14:53 ` Markus Klotzbücher
2008-10-23 18:53 ` Adam Graham
2008-10-23 18:38 ` Adam Graham
2008-10-23 18:21 ` Adam Graham
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=200810231330.08865.sr@denx.de \
--to=sr@denx.de \
--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