On Thursday 28 October 2004 20:29, bandwidthcrunch wrote:
> Hi All,
>         I been working on a 2.4.19 kernel with a 2002 mtd snapshot(yes
> old but only one working with 2.4.19 for right now :( ) .I have a
> samsung k9F1208U0M nand chip on a custom pxa hardware.
> dmesg shows me that a mtd partition has been detected
> 0x00000000-0x00040000 : "Bootloader"
> 0x00040000-0x00140000 : "Kernel"
> 0x00140000-0x02000000 : "Filesystem"
> NAND device: Manufacture ID: 0xec, Chip ID: 0x76 (Samsung K9D1208V0M)
> Creating 1 MTD partitions on "Samsung K9D1208V0M":
> 0x00000000-0x02000000 : "Filesystem on nand"
>
> [root@manav /root]#cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00040000 00040000 "Bootloader"
> mtd1: 00100000 00040000 "Kernel"
> mtd2: 01ec0000 00040000 "Filesystem"
> mtd3: 02000000 00004000 "Filesystem on nand"
>
> but when i do a
> [root@manav /root]#cat /proc/yaffs
> YAFFS built:Oct 28 2004 11:35:04
> $Id: yaffs_fs.c,v 1.35 2004/10/20 20:12:43 charles Exp $
> $Id: yaffs_guts.c,v 1.37 2004/10/20 20:12:43 charles Exp $
>
> and thats it .
> mkyaffs /dev/mtd3 does try to format the device but ends up getting a
>
> nand_read_oob: from = 0x00444000, len = 16
> nand_read_oob 1: col = 0, page=2220
> Erasing block at 0x08444000
>
> nand_read_oob: from = 0x00448000, len = 16
> nand_read_oob 1: col = 0, page=2240
> Block at 0x08448000 is damaged and is not being formatted
>
> and mkyaffs -e /dev/mtd3 sample.yaffs gives
> [root@manav /root]#./mkyaffs -e /dev/mtd3 root-balloon-base.yaffs
> Image not a multiple of 528 bytes

Perhaps the image you are loading was damaged somehow. An image should be a 
multiple of the  NAND page size (512 + 16) = 528 bytes.

>
> Shouldnt my /proc/yaffs be showing some entries ?Any clues what is
> happening in here ?

/proc/yaffs will only show extra info once a yaffs device is mounted.

>
> regards,
> band
>
> _______________________________________________
> yaffs mailing list
> yaffs@stoneboat.aleph1.co.uk
> http://stoneboat.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs