All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivan Djelic <ivan.djelic@parrot.com>
To: "Philip, Avinash" <avinashphilip@ti.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: mtd oob test is failing consistently at same places in NAND flash
Date: Tue, 8 May 2012 15:23:54 +0200	[thread overview]
Message-ID: <20120508132354.GA16164@parrot.com> (raw)
In-Reply-To: <518397C60809E147AF5323E0420B992E3E934BF1@DBDE01.ent.ti.com>

On Tue, May 08, 2012 at 01:33:06PM +0100, Philip, Avinash wrote:
> Hi,
> 
> We are having an 8-bit NAND part (MT29F2G08ABAEAWP from Micron) connected to GPMC
> Module (General purpose memory controller) from TI.

Hi,
How is ecc performed ?
Using NAND internal ecc ? or with GPMC 1-bit Hamming ? 4-bit/8-bit BCH ?
Which version of omap2 driver are you using ?
Is OOB also ECC-protected ?

> We have been seeing mtd_oobtest failure on a partition size of 248 MB. Most of
> the time, test case 2 of mtd_oobtest is failing. On debugging further it seems
> that bit flip is happening on the test case 2 in OOB area. It is observed that
> the failure locations are consistent. 

If you are able to reproduce failures, then you should be able to tell which bits
in OOB are failing, by adding a few debugging lines in the code.

> To verify further we had tried writing zeros to OOB area and read it back. 
> This test is passing and confirms that all OOB bits (that are programmable)
> are not bad.

It does not confirm anything, bits can fail by remaining stuck at 0.

BR,
--
Ivan

  reply	other threads:[~2012-05-08 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 12:33 mtd oob test is failing consistently at same places in NAND flash Philip, Avinash
2012-05-08 13:23 ` Ivan Djelic [this message]
2012-05-08 15:09   ` Philip, Avinash
2012-05-08 15:23     ` Philip, Avinash
2012-05-08 18:45     ` Ivan Djelic
2012-05-09 15:12       ` Philip, Avinash
2012-05-09 15:24         ` Ivan Djelic
2012-05-09 15:46           ` Philip, Avinash
2012-05-09 16:05             ` Ivan Djelic
2012-05-10  7:51             ` Ricard Wanderlof
2012-05-09  6:37     ` Ricard Wanderlof
2012-05-10 13:01 ` Artem Bityutskiy

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=20120508132354.GA16164@parrot.com \
    --to=ivan.djelic@parrot.com \
    --cc=avinashphilip@ti.com \
    --cc=linux-mtd@lists.infradead.org \
    /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.