NAND bbt build reads wrong oob data
tpoynor at mvista.com
Fri Jul 15 03:58:48 EDT 2005
Thomas Gleixner wrote:
> On Thu, 2005-07-14 at 20:19 -0700, Todd Poynor wrote:
>>The value read seems to be a different byte, perhaps offset 14 instead
>>of offset 5 as specified by the placement scheme. The hack that seems
>>to fix it for me, namely to read the whole OOB area instead of the
>>individual byte, is below.
> That's pretty strange. Which chip type are you using ?
NAND device: Manufacturer ID: 0xec, Chip ID: 0x45 (Samsung NAND 32MiB
using omap-nand-flash.c driver from OMAP community tree
linux-omap-2.6.git at source.mvista.com (which is slated for sending to
linux-mtd after conversion of board specifics to LDM platform device stuff).
OK, this is pretty unexpected, so I'll try harder to figure out where it
goes wrong or whether I've got another board that it affects (a
colleague reported some new bad blocks messages after upgrading to the
same software on a different board, will see if there's a similar
>>NAND_BBT_SCAN2NDPAGE is triggering a BUG I haven't investigated yet.)
> You introduced it by setting readlen = mtd->ooblock. I know that the
> name of this is confusing. oobblock is the page size. So readlen is >
More information about the linux-mtd