Problems with Jffs2 on this board

Problems with Jffs2 on this board

[Esben Nielsen]

I am trying to board Linux to my company's StrongARM based board.
I am now using bootldr 2_18_45 from handhelds.org, mkfs.jffs2 revision 1.17 
and HardHat's Linux-2.4.2_hhl20.

I create a root filesystem image with mkfs.jffs2 which I transfer to the 
flash on the board with over serial. I can now boot the kernel from the 
bootloader but the kernel can't find other files that those in /devs (from 
the debug level of 2 in the jffs2 subsystem in the kernel) and thus
fails to call /sbin/init.
Now I see with "ls" in the bootldr that that can't see other subfiles that 
/devs/*, /boot/zImage and a few in /bin, either!
Thus I suspect very much that my mkfs.jffs2 is broken - I downloaded it
binary from www.redhat.com. Now, I try to compile a new one from the
latest from CVS on infradead.org. But I simply can't make it compile, as
I get:

compr_zlib.c:15:2: #error "The userspace support got too messy and was 
removed. Update your mkfs.jffs2"

What do I do about that? Do I have to go through my kernel on my host
machine to create a proper jffs2 image?

Esben Nielsen
Cotas Computer Technology A/S

Re: Problems with Jffs2 on this board

[David Woodhouse]

esn@cotas.dk said:
>  Now, I try to compile a new one from the latest from CVS on
> infradead.org. But I simply can't make it compile, as I get:

> compr_zlib.c:15:2: #error "The userspace support got too messy and was
>  removed. Update your mkfs.jffs2"

cd mtd/util ; rm compr_zlib.c ; cvs up compr_zlib.c

It used to be a symlink to the kernel one. Now it isn't. CVS will have got 
upset and refused to put the next file there because the symlink is in the 
way.

--
dwmw2

Re: Problems with Jffs2 on this board

[David Woodhouse]

esn@cotas.dk said:
>  I create a root filesystem image with mkfs.jffs2 which I transfer to
> the  flash on the board with over serial. I can now boot the kernel
> from the  bootloader but the kernel can't find other files that those
> in /devs (from  the debug level of 2 in the jffs2 subsystem in the
> kernel) and thus fails to call /sbin/init.

Your mkfs.jffs2 isn't the problem though -- can you double-check that the 
image has made it correctly to the flash? If you can boot nfsroot, read it 
back from the /dev/mtd device and compare it with the original -- to verify 
correct download and correct partitioning setup etc.

--
dwmw2