A suggestion: use nanddump to watch what is really burned into flash.
Most probably yaffs tags is not in its place, which is 2 bytes offset
within oob area.
And if the image from nanddump is not compatible with YAFFS image, you may
have a check of your NAND driver.
Maybe the OOB area are already taken by NAND driver and there's not enough space
for YAFFS.
Another suggestion is to use yaffs with inband-tags, but it still
needs a tweak for current
mkyaffs2image source code.
On Mon, Aug 17, 2009 at 8:07 PM, Voser,
Peter<
Peter.Voser@albistechnologies.com> wrote:
> Hello,
>
> I saw several other questions to this topic, but I can't make it run…
>
> I would like to create a YAFFS image using mkyaffs2image for creation and
> the MTD utility nandwrite for programming under 2.6.22.18:
>
> $mkyaffs2image testdir yaffs2.img
> $nandwrite -a -o yaffs2.img /dev/mtd5
>
> After mounting, the device has no checkpoint and is empty (only "lost+found"
> visible).
>
> What I tried out:
> 1) I already tried the mkyaffs2image patch with the new oob_ecc_size (=14)
> parameter from here
> http://www.aleph1.co.uk/lurker/message/20070912.140012.12f2d093.en.html .
> 2) Also I already wanted to try the yaffs_mtdif2.c in the patches folder -
> but it doesn't compile with my 2.6.22.18 MTD environment. Anybody has a
> newer version?
>
> Any other ideas?
>
> Thank you very much,
> Peter Voser
>
>
> _______________________________________________
> yaffs mailing list
> yaffs@lists.aleph1.co.uk
> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
>
>
--
Regards, Shizheng
(text/plain)