From: Juergen Beisert <jbe@pengutronix.de>
To: barebox@lists.infradead.org, marc@cpdesign.com.au
Subject: Re: Way to clear nand bad block table
Date: Thu, 26 Jul 2012 11:27:48 +0200 [thread overview]
Message-ID: <201207261127.48919.jbe@pengutronix.de> (raw)
In-Reply-To: <002601cd6b08$37498d50$a5dca7f0$@cpdesign.com.au>
HI Marc,
Marc Reilly wrote:
> Is there a way to clear the nand bad block table?
>
> I'm not sure what happened, but I was playing around with barebox init and
> didn't register the nand device - then when I booted the kernel there were
> a stack of UBI errors.
> I assume this also did something to the bbt as subsequent barebox startups
> give a heap of bad block messages. Note not all blocks are bad - tested
> with nandtest and there's still some R/W going on.
> All the code I looked at seemed to indicate that once a block is marked bad
> you can't go back.
>
> Any ideas much appreciated.
The flash blocks which contains the "bad block table" are protected by
the "bad block table" aware MTD layer.
So, the ugly way: run a bootloader which does not use the in-flash bad block
table. Then the tables are regular blocks in the flash and can be erased.
After that run again the bad block table aware bootloader and it will
re-create the in-flash table. But be careful: In this case the generic
functions scans all blocks in the NAND to collect the bad block markers in
each NAND block's OOB. If this information is already destroyed somehow, this
solution does not help.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-07-26 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 8:25 Marc Reilly
2012-07-26 9:27 ` Juergen Beisert [this message]
2012-07-27 1:24 ` Marc Reilly
2012-07-27 7:53 ` Sascha Hauer
2012-07-27 8:31 ` RFC: How to setup and handle NAND flashes in Barebox Juergen Beisert
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=201207261127.48919.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=marc@cpdesign.com.au \
/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