bad block on mtd

hi bhodi,
in your install instructions you write:

>4. Be sure there is no bad block in the first 2M of your NAND (check dmesg for bad block 0 to 16). This is very important, if >there is bad block in the first 2M, don't flash u-boot, because you will almost certainly brick your box. Please post your >question here (there is a work around for it).

and:

>13. For sanity check, print out uBoot envs to see if they were flashed OK. If there is error in listing the envs, do not reboot and >post your problem here.

are these workarounds already discussed? if yes, where?
how can i remap or exclude such bad blocks? or how is it solved?

tnx
jay

jay,

The workaround is specific to the bad blocks case. Ie. whether they are in the middle of the area where we need to write u-boot or u-boot envs or kernel image. We don't remap them, just make sure the data are written successfully. Basically, nandwrite skips bad blocks and bootROM knows how to read u-boot image with bad blocks.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

another useful post from bodhi about bad blocks http://forum.doozan.com/read.php?2,7806,13250#msg-13250

Might be a good idea to make a post you can add to the list of tutorials

bobafetthotmail Wrote:
-------------------------------------------------------
> another useful post from bodhi about bad blocks
> http://forum.doozan.com/read.php?2,7806,13250#msg-
> 13250
>
> Might be a good idea to make a post you can add to
> the list of tutorials

Thanks! I forgot about this post.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)