Ok, so i determined that because of the 512 blocksize on my device, it's
actually a yaffs-1 image. Still, I've tried using mkyffsimage and still,
nothing appears at all in / -- linux halts saying that it can't find
/sbin/init, and again, when I mount the mtdblock device under the same
kernel (first using nfs root) then all i see is 'lost+found'.
Has anyone on this list used RedBoot to write a yaffs filesystem to
flash? If so, how?
My host system is x86. My target system is arm, little-endian.
I've tried both using an x86-compiled mkyaffsimage and an arm-compiled
mkyaffsimage, but neither seem to work, although they say they're adding
all of the files.
Say a directory exists called 'newroot' which contains all of the arm
filesystem that I want to create. I use:
mkyaffsimage newroot ../new_root.yaffs
Then with RedBoot, I use
fis delete ...
load ...
fis write ...
Am I missing some crucial step?
~/Chris
Christopher Friedt wrote:
> This might sound like a really, really over-answered FAQ, but how does
> one actually go about creating a yaffs2 image?
>
> I used mkyaffs2image on a directory, received a file image in return,
> and there were no error codes on exit. However, After writing that image
> to flash with RedBoot, launching into an NFS root, and mounting the
> flash device, absolutely nothing shows up within the directory aside
> form 'lost+found'.
>
> Could anyone offer some instruction as to how I could write a yaffs2
> image to flash 'properly' ?
>
>
> ~/Chris
>
> _______________________________________________
> yaffs mailing list
> yaffs@lists.aleph1.co.uk
> http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs
>
>
(text/plain)