Hi guys,

I hate to ask for help so early into a project, but I'm at the hair-pulling stage already...

I'm using the 9260-EK board, and trying to boot linux with the root device specified as one of the MTD partitions in the NAND device. If I copy an ext3 file-system into the partition, everything starts up perfect. If I copy the same file-system in jffs2 format however, I get the errors below and the board locks up.

To see what the jffs partition looks like, I booted with the working ext3 root instead, and then mounted the jffs partition to /mnt. I got the same jffs errors as before, but it finished mounting nonetheless, and I could cd into it and everything looked ok.

The jffs partition is being made with this command line:

mkfs.jffs2 -d ./root -p -s 0x800 -e 0x20000 -n -l -o /fs.bin

I'm using SAM-BA to write the image into the NAND partition.

Everything was created with buildroot.

Does anybody have any ideas about what's happening?

Thank-you!

--Imre M.

------------------------------------------------------------------

jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc418: 0x04f0 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc41c: 0x0800 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc420: 0x0006 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc424: 0x240c instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc428: 0xdfc0 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc42c: 0x5e78 instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc430: 0x684f instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc434: 0xfe1c instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc438: 0xccdd instead
jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x001bc43c: 0x264d instead
Further such events for this erase block will not be printed
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 112K
Warning: unable to open an initial console.

We use the following mkfs.jffs2 options :
--pad --little-endian --eraseblock=0x20000 -n

Are you using SAM-BA 2.6 ?

try erasing the whole partition from linux (flash_eraseall) and mounting the clean partition as jffs2 (-t jffs2). Then copy all your data to the partition. If this works, your flash image has wrong block size etc. If not, your flash is not working correctly (either the chip or the driver).

try to see that u have got the dev directory in the RFS
and it has the basic debug node.

What I would like to know is how you were able to get buildroot to finish. I have been working with buildroot for the past month and a half and have yet to get buildroot to complete. Either it can't find a sourcefile, or it has trouble building a jffs RFS file. And now it's complaining about "no mail command" during the fakeroot portion of the build. I have been filing bug reports but nothing is getting fixed. I have been forced to buy a Timesys license and am trying to figure out how to use those tools now.

I would be interested to see how you get on the the TimeSys tools - I couldnt get around the inconsistent depencies of their RPMs.

About building, an RFS, see my recent post on using a Debian RFS, using QEMU.

Gertjan

Well, I'm not using the web-based build tools, just the files. So far I have been able to compile a kernel and replace the kernel in the SAM-BA BSP download and get it to work. I even added some components that aren't in the BSP build. Still waiting for a document to how to build the RFS and Busy-Box by hand.