public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "David A. Marlin" <dmarlin@redhat.com>
To: manningc2@actrix.gen.nz
Cc: Thomas Gleixner <tglx@linutronix.de>,
	MTD List <linux-mtd@lists.infradead.org>
Subject: Re: NAND fail testing
Date: Thu, 13 Jan 2005 12:11:43 -0600	[thread overview]
Message-ID: <41E6B9DF.3000707@redhat.com> (raw)
In-Reply-To: <20050113174617.4786F4188@blood.actrix.co.nz>


Charles:

Thank you for your reply.  Some additional information, the chips I am 
using are Renesas AG-AND (HN29V1G91T-30).  It was a note from Renesas 
that suggested this approach to permit erase/write fail testing.  I 
think this chip permits a "Random Data Input" operation that would 
permit writing a single byte, but I need to confirm this.  Since this 
does not appear to be a feature shared with other NAND/AND chips, it 
seems I may not be able to use our current driver/utilities to 
accomplish it (without modification).

Charles Manning wrote:
> I suggest you read the Toshiba NAND design guide before you try things like 
> this. Google for "toshiba nand flash applications design guide"
> 
> NAND is always written in a per-page mode, even if you only change a single 
> byte. Attempting what you propose will not only wear the single byte, but 
> will wear the whole page and block.
> 
> IMHO the best way to do testing is to emulate a device in RAM. It is 
> relatively simple to modify RAM contents and force the higher level to do its 
> test stuff. Trying to do it with a real hardware failure will take a long 
> time and is far harder to reproduce etc.

Agreed, but part of the testing is reading error status information back 
from the chips after the erase/write fail and determining if hardware 
ECC is possible.  I have not tried to emulate this device in RAM, but I 
don't think it is a viable option for me since producing and reading 
these error codes are part of the testing I need to perform.


Thanks again,

d.marlin

  reply	other threads:[~2005-01-13 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13 15:55 NAND fail testing David A. Marlin
2005-01-13 17:48 ` Thomas Gleixner
2005-01-13 17:56   ` David A. Marlin
2005-01-13 18:15     ` Thomas Gleixner
2005-01-13 18:24       ` Artem B. Bityuckiy
2005-01-13 17:52 ` Charles Manning
2005-01-13 18:11   ` David A. Marlin [this message]
2005-01-13 18:12 ` Michael

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=41E6B9DF.3000707@redhat.com \
    --to=dmarlin@redhat.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=manningc2@actrix.gen.nz \
    --cc=tglx@linutronix.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