[U-Boot] handling of NAND blocks which go bad

[U-Boot] handling of NAND blocks which go bad

[tkoka]

I have a question about how u-boot handles NAND blocks going bad over
time, for example when uncorrectable ECC errors or erase failures are
encountered for blocks which are not already in the Bad Block Table.  I
know that u-boot properly skips already known bad blocks, but I can't
seem to find where new bad blocks are recorded in the BBT.  Can anyone
point me in the right direction?  Or confirm that this is not supported
in u-boot?  I am using a BSP from Freescale on a custom mx25 board, but
I cannot find this handling in the latest u-boot git either.

TIA

[U-Boot] handling of NAND blocks which go bad

[Wolfgang Denk]

Dear tkoka,

In message <1310616218.8257.10.camel@localhost> you wrote:
> I have a question about how u-boot handles NAND blocks going bad over
> time, for example when uncorrectable ECC errors or erase failures are
> encountered for blocks which are not already in the Bad Block Table.  I
> know that u-boot properly skips already known bad blocks, but I can't
> seem to find where new bad blocks are recorded in the BBT.  Can anyone
> point me in the right direction?  Or confirm that this is not supported
> in u-boot?  I am using a BSP from Freescale on a custom mx25 board, but
> I cannot find this handling in the latest u-boot git either.

If you are looking into reliable systems based on NAND technology, you
want to use UBI / UBIFS - even to the extent that you load the U-Boot
image from a (static) UBI volume.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
A consultant is a person who borrows your watch, tells you what  time
it is, pockets the watch, and sends you a bill for it.