On Thursday 09 November 2006 22:57, Aubrey wrote:
> On 11/9/06, Charles Manning <manningc2@actrix.gen.nz> wrote:
> > > 2) The same driver, If I change the nand chip to NAND01GW3B, which is
> > > 1Gbit, 2k byte page, I got every blocks are bad. I think there should
> > > be something wrong in my driver. Is there any existing mtd-nand driver
> > > support 2K page nand flash?
> >
> > This part should work with yaffs2. yaffs2 supports checkpointing, so
> > remounts should be way faster.
> >
> > Did you erase the part first?
>
> Yes, I erase it first everytime.
>
> > If you're seeing bad blocks then most likely:
> > 1) You did not erase the part first.
> > - or -
> > 2) Your driver is bad.
>
> Here is kernel bootup log on my side.
> It can read manufacurer ID correct, so I assume my driver works properly.
> Thanks for your any suggestion.
> =================================================================
> NAND device: Manufacturer ID: 0x20, Chip ID: 0xf1 (ST Micro NAND
> 128MiB 3,3V 8-bit)
> Scanning device for bad blocks
> Bad eraseblock 0 at 0x00000000
> Bad eraseblock 1 at 0x00020000
> Bad eraseblock 2 at 0x00040000
> Bad eraseblock 3 at 0x00060000
> Bad eraseblock 4 at 0x00080000
> Bad eraseblock 5 at 0x000a0000
> Bad eraseblock 6 at 0x000c0000
> Bad eraseblock 7 at 0x000e0000
> Bad eraseblock 8 at 0x00100000
> Bad eraseblock 9 at 0x00120000
> ----snip----
Looks almost certainly a driver issue. Pretty much guarantee that either:
1) Your driver is bad and is telling yaffs that blocks are bad when they are 
not.
- or -
2) The erase is not working, 

I suggest:
1) adding some printk's to the mtd nand  block_is_bad function
2) Turning on YAFFS_TRACE_MTD.

-- CHarles