All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dimitar Penev <dpn@switchfin.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND flash -  bad blocks
Date: Thu, 10 Jan 2013 09:56:30 +0200	[thread overview]
Message-ID: <002f01cdef08$009f0210$2901a8c0@dpn> (raw)

Hello,

First of all sorry if this question was already answered here.

We are sourcing some K9F8G08U0M-PIB0 NAND flash devices.
On the first erase in uboot 2011.09 I got bunch of mostly consecutive bad 
blocks.
According to the datasheet we should get not more then 80 bad blocks for our 
chip
but I get something like 240 bad blocks for most of the NAND chips.

I seems to be able to fix this using the following procedure:

In uboot
uboot>nand scrub.chip

In uboot
uboot>nand erase.chip clean
at this point I get usually 1,2 bad blocks which looks normal to me.

In Linux we have few mtd partitions on this NAND chip.
Unmount all of them and for all of them :
linux>nandtest -m /dev/mtdx
Usually this doesn't add any new badblocks on top of what I get on nand 
erase in uboot,
but I really haven't tested that much device to say.

After this procedure the NAND flash seems to work fine.
Do you think this is reliable way?
Is there something better I can do?

Has anyone got NAND component batch having more bad blocks then datasheet 
allows.
Should we consider the provider unreliable?

Thank you
Dimitar 

             reply	other threads:[~2013-01-10  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10  7:56 Dimitar Penev [this message]
2013-01-10 19:19 ` [U-Boot] NAND flash - bad blocks Scott Wood
2013-01-11  8:46   ` Dimitar Penev
2013-01-11 20:21     ` Scott Wood
2013-01-15 11:09       ` Dimitar Penev
2013-01-15 17:33         ` Scott Wood

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='002f01cdef08$009f0210$2901a8c0@dpn' \
    --to=dpn@switchfin.org \
    --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.