From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Memory testing of flash
Date: Tue, 31 Jan 2012 12:41:09 +0100 [thread overview]
Message-ID: <20120131114109.8F5A11222340@gemini.denx.de> (raw)
In-Reply-To: <loom.20120131T094437-306@post.gmane.org>
Dear vk,
In message <loom.20120131T094437-306@post.gmane.org> you wrote:
> Is it safer to test flash during bootup...what if power gets off half a way
> while writing data on address at which uboot source code is located?Then uboot
> will never get started??
Write testing of flash devices on a regular base (like as part of the
POST at every power-on or even at every boot cycle has never been a
clever idea. It is risky. And I doubt if people who design such a
test understant the failure mechanisms of such devices, and what can
be done to prevent problems.
In most cases I've seen so far the tests did not do anything good.
They only reduced the life time of the devices. A really stupid thing
to do.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The first 90% of a project takes 90% of the time, the last 10% takes
the other 90% of the time.
next prev parent reply other threads:[~2012-01-31 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 8:46 [U-Boot] Memory testing of flash vk
2012-01-31 11:41 ` Wolfgang Denk [this message]
[not found] ` <CAHD55i3Odt_e9PdEAoyE=JhRwb5jaKem=xp7PRB-Oe1rqN9EJg@mail.gmail.com>
2012-01-31 15:47 ` Wolfgang Denk
[not found] ` <CAHD55i12Pbk+8RD+MrBaquQPE79UFVy8kRD5jMiNQh81CB06xQ@mail.gmail.com>
[not found] ` <20120201102956.09F9225E9F5@gemini.denx.de>
2012-02-01 12:40 ` 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=20120131114109.8F5A11222340@gemini.denx.de \
--to=wd@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