Arvind,
You might like to try a version I put together recently
to run on 2.6.21, see
http://users.actrix.co.nz/manningc/yaffs2-ian-20070523.tgz.
You do not need the stuff for 9BYTE_TAGS that I added to
this, but it also includes a change to the MTD interface
that I needed on 2.6.21-rc6.
BTW: if the NAND bad block markings are screwed up you will
need to hack MTD to let you erase these blocks to recover them.
I always recommend disabling the MTD's bad-block marking when
bringing up a new board/platform and to record the NAND chips
bad-block list before you start.
-Ian
On Tuesday 19 June 2007 16:00, you wrote:
> we are using YAFFS2 on 256 MB ST Micro Nand Flash.
> Few times we have seen when the unit is powered up and tries
> to mount the YAFFS2 files system, most of the blocks are
> marked bad and then every time on mount it displays the
> messages
> "Partially written block XXXX being set for retirement".
>
> And all of these blocks are now MARKED BAD in NAND BBT.
http://users.actrix.co.nz/manningc/yaffs2-ian-20070523.tgz
>
> we are usinh a mix of JFFS2 on small "ROOT FS" partition and
> YAFFS2 on larger (200MB+) partition
> All other partitions are fine at this point.
>
> The Configuration we are using is
>
> PXA255
> ST Micro 256MB large page NAND Flash
>
> Linux 2.6.20.3
>
> YAFFS2 - Yaffs_checkptrw.c, v 1.13 2007/02/14
> YAFFS_CHECKPOINT_VERSION 2
>
> yaffs_guts.c, v 1.48 2007/03/12
>
> yaffs_ecc.c v 1.9 2007/02/14
>
>
>
> NAND Flash is partitioned as
>
> 0000 - 0x20000 ---> System Area
> 0x20000 - 0x100000 ---> Control
> 0x100000-0x300000 ----> kernel
>
> 0x300000-0x1300000 ---> Root File system ---- JFFS2
>
> 0x1300000-0xEE00000 ---> User File System ---- YAFFS2
>
>
> Any Ideas? Does anybody else has seen similar issues
>
> Any help is greatly appreciated.
>
>
> thanks,
>
> Arvind
>
>
>
> _______________________________________________
> yaffs mailing list
> yaffs@lists.aleph1.co.uk
> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
(text/plain)