From: Ira W. Snyder <iws@ovro.caltech.edu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/7] 83xx/85xx/86xx: Add ECC support
Date: Mon, 9 Nov 2009 18:15:26 -0800 [thread overview]
Message-ID: <20091110021525.GB407@ovro.caltech.edu> (raw)
In-Reply-To: <1257816026.10661.51.camel@localhost.localdomain>
On Mon, Nov 09, 2009 at 07:20:26PM -0600, Peter Tyser wrote:
> On Tue, 2009-11-10 at 09:08 +0800, Liu Dave-R63238 wrote:
> > > On Tue, 2009-11-10 at 08:42 +0800, Liu Dave-R63238 wrote:
> > > > > IIRC, 85xx cache is enabled, so when we do the ecc error inject
> > > > > test, What will happen before disable ecc error inject?
> > > > > I-fetch may get wrong instruction?
> > >
> > > If you're injecting multibit errors, yes, things could break
> > > down, much like a real multibit error.
> >
> > IIRC, 83xx ECC code will NOT break down when we inject multibit error.
> > The code will go on, u-boot also go on...
>
> What is the benefit of having such a high level of control over error
> injection? When do people use this feature? How often do they use it?
>
I used the ECC error injection code when adding ECC support on our
board, to verify that ECC was actually enabled and reporting errors. I
found it extremely useful at the time, though I haven't used it since.
> > > > and ....
> > > > Because cache is enabled, data bus assume 64 bits (it is
> > > normal case).
> > > > The DDR bus will have 4-beat burst. So the error
> > > information will be
> > > > the last beat triggered, or multi-bit error at first beat....., or..
> > > > It is really complex.....
> > >
> > > I believe all 4 beats would have the ecc error injected.
> > >
> > > In my opinion, the error reporting functionality of the ECC
> > > code is much more important than error injection. Other than
> > > testing code during development, when do you inject errors?
> > > ECC detection and reporting is useful day-to-day, in the
> > > field, during manufacturing tests, etc so that's where the
> > > emphasis of this patch is focussed.
> >
> > 83xx ECC code also has good ECC error reporting functionality,
> > IIRC, type ecc status...
>
> I believe the ecc status command basically just did a register dump of
> the ECC registers. In my opinion, the output was overly verbose and not
> that useful. The patch I submitted attempts to *decode* the register
> dump so Joe User can figure out what's really wrong with their board.
>
I haven't looked at your code. When I was running the old ecc command, I
had the 83xx reference manual open to decode the command's output, IIRC.
PS - I'm happy to test stuff on 83xx, I'll try and find time to test
this patch series tomorrow.
Ira
next prev parent reply other threads:[~2009-11-10 2:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 23:37 [U-Boot] [PATCH v2 0/7] 83xx/85xx/86xx ECC update Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 1/7] 83xx: Add CCSR DDR register offsets Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 2/7] 85xx/86xx: Add ECC error injection defines Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 3/7] 83xx/85xx/86xx: Add ECC support Peter Tyser
2009-11-10 0:25 ` Liu Dave-R63238
2009-11-10 0:32 ` Peter Tyser
2009-11-10 0:38 ` Liu Dave-R63238
2009-11-10 0:42 ` Liu Dave-R63238
2009-11-10 0:46 ` Liu Dave-R63238
2009-11-10 1:01 ` Peter Tyser
2009-11-10 1:08 ` Liu Dave-R63238
2009-11-10 1:20 ` Peter Tyser
2009-11-10 2:15 ` Ira W. Snyder [this message]
2009-11-10 3:07 ` Peter Tyser
2009-11-10 16:51 ` Ira W. Snyder
2009-11-10 17:36 ` Peter Tyser
2009-11-10 17:53 ` Ira W. Snyder
2009-11-09 23:37 ` [U-Boot] [PATCH 4/7] 83xx: Migrate CONFIG_DDR_ECC_CMD to CONFIG_EDAC_FSL_ECC Peter Tyser
2009-11-10 0:51 ` [U-Boot] [PATCH 4/7] 83xx: Migrate CONFIG_DDR_ECC_CMD toCONFIG_EDAC_FSL_ECC Liu Dave-R63238
2009-11-10 1:09 ` Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 5/7] Add check for ECC errors during SDRAM POST and mtest Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 6/7] xes: Add 8xxx post support Peter Tyser
2009-11-09 23:37 ` [U-Boot] [PATCH 7/7] xes: Enable memory POST and ECC error reporting Peter Tyser
2009-12-16 15:55 ` [U-Boot] [PATCH v2 0/7] 83xx/85xx/86xx ECC update Peter Tyser
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=20091110021525.GB407@ovro.caltech.edu \
--to=iws@ovro.caltech.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.