All of lore.kernel.org
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] flash post test
Date: Mon, 06 Feb 2012 23:59:17 +0100	[thread overview]
Message-ID: <4F305B45.10104@aribaud.net> (raw)
In-Reply-To: <4F305A5A.80607@freescale.com>

Hi Scott,

Le 06/02/2012 23:55, Scott Wood a ?crit :
> On 02/06/2012 04:23 PM, Albert ARIBAUD wrote:
>> Hi Vaibhav,
>>
>> Le 06/02/2012 05:57, vaibhav kothari a ?crit :
>>> hi albert
>>>
>>> Yes,actually there is already support of flash test in POST of latest
>>> uboot.They are testing flash on every power on so am I for my board.But i
>>> don't want to disturb sectors in which uboot code relies. Can you help me
>>> here?
>>
>> I am no NAND specialist, but I do hope NAND POST tests are pure read
>> tests and thus are not affected by poweroffs (and can actually test any
>> part of NAND).
>
> NAND has a property called "read disturb", where excessively reading a
> sector without writing to it can eventually cause data loss.  U-Boot is
> already read once per boot, but reading it a second time could halve the
> expected lifetime.  Data managed by something like ubi is be scrubbed in
> a way that avoids this, but U-Boot itself is not usually managed in this
> way (boot hardware/rom does not understand ubi).

I *did* say I am not a NAND expert. :)

Thanks Scott. But then, isn't NAND testing a kind of catch-22, where by 
actually tesing if NAND works it one ends up weakening it either through 
read disturb, or simply through writes?

> -Scott

Amicalement,
-- 
Albert.

  reply	other threads:[~2012-02-06 22:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-31  9:27 [U-Boot] flash post test vk
2012-02-03 21:32 ` Albert ARIBAUD
2012-02-06  4:57   ` vaibhav kothari
2012-02-06 22:23     ` Albert ARIBAUD
2012-02-06 22:55       ` Scott Wood
2012-02-06 22:59         ` Albert ARIBAUD [this message]
2012-02-06 23:02           ` Scott Wood
2012-02-07  4:32             ` vaibhav kothari

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=4F305B45.10104@aribaud.net \
    --to=albert.u.boot@aribaud.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 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.