[U-Boot] handling of bad blocks in nand
Arno Steffen
arno.steffen at googlemail.com
Thu Jun 24 08:28:30 CEST 2010
2010/6/23 Scott Wood <scottwood at freescale.com>:
> On Wed, Jun 23, 2010 at 02:40:51PM +0200, Arno Steffen wrote:
>> A short question to handling of bad blocks:
>> My nand shows a few bad blocks (example 100000)
>>
>> What is happen when I write / read from that block via nand write / read.
>> Is content than ok (by mapping good blocks do that address)?
>
> Bad blocks are skipped, and all subsequent blocks are shifted out by one.
>
>> Other way around - if I have commands like
>>
>> "get_kn=nand read.i 0x80000000 c0000 200000"
>>
>> do I have to care for bad blocks in that range ?
>> Di I have to make the part bigger to have some extra blocks, if one is
>> skipped while write/read as it is bad?
>
> The partition must be at least as large as the number of real data blocks
> you want to write, plus the number of bad blocks within that range.
>
> -Scott
>
Thanks Scott,
does it mean in other words - I don't have to care for the bad block,
can write on the bad block address as it would be ok?
The only thing I have to care is, that I have leave enough space
between the partitions. As for instance : I need 10 blocks for a
certain filesystem, give it 12 ? So it could correct 2 bad blocks in
this range.
Best regards
Arno
More information about the U-Boot
mailing list