public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Memory Testing (Flash,EEPROM)
Date: Wed, 27 Oct 2004 20:48:48 +0200	[thread overview]
Message-ID: <20041027184853.1ABB0C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 27 Oct 2004 19:14:34 +0200." <1CFEB358338412458B21FAA0D78FE86D4F0C68@rennsmail02.eu.thmulti.com>

In message <1CFEB358338412458B21FAA0D78FE86D4F0C68@rennsmail02.eu.thmulti.com> you wrote:
> Wolfgang Denk wrote:
> > It makes no real sense to perform a write testing  on  flash  memory,
> > for  example,  as  you must erase the flash to write it, and erase it
> > again to write it again, and the fact that you can write it now is no
> > guarantee that it is still erasable the next time.
> 
> IMHO, the point is not to test the chip, but to test the wires to the chip,
> for industrial purpose.

You don't want to do this  in  software  -  software  can  only  test
certain  functions,  but not all connections. For that you want to do
standard hardware verification procedures like boundary scan etc.

> For the other matters, the customer will find it out by himself anyway :*)

Indeed ;-)

Best regards,

Wolfgang Denk

-- 
See us @ Embedded/Electronica Munich, Nov 09 - 12, Hall A.6 Booth 513
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Successful and fortunate crime is called virtue.             - Seneca

  reply	other threads:[~2004-10-27 18:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-27 17:14 [U-Boot-Users] Memory Testing (Flash,EEPROM) Fillod Stephane
2004-10-27 18:48 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-27 11:53 Vikrant_Basotra
2004-10-27 14:27 ` Wolfgang Denk

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=20041027184853.1ABB0C1430@atlas.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