AT91SAM9263 JFFS2 problems
Hi, has anyone seen problems booting an AT91SAM9263-EK board with the JFFS2 filesystem created by buildroot? I used to be able to boot no problem with an older version of buildroot, but not with the latest. I'm getting the following kernel panic:
VFS: Mounted root (jffs2 filesystem).
Freeing init memory: 136K
Warning: unable to open an initial console.
Kernel panic - not syncing: No init found. Try passing init= option to kernel.
I've loaded the NAND flash as follows:
0x00000000 - at91bootstrap0x00020000 - u-boot0x00200000 - kernel0x00400000 - JFFS2
My bootargs are "mem=64M console=ttyS0,115200 root=/dev/mtdblock1 rw rootfstype=jffs2"
The strange thing is if I change the bootargs to root=/dev/mtdblock0, I get a ton of jffs2 oob and ecc errors, but after a while, it gives me the login prompt.
My JFFS2 memory type options are:
Page Size: 0x800 Erase Block Size: 0x20000
Not using clean marker.
These options never gave me a problem before.
The only other thing I can think of is a message I get after a build of buildroot about skipping dev, tmp, and etc while creating the RFS:
table='target/device/Atmel/root/device_table.txt'
mkfs.jffs2: skipping device_table entry '/dev': no parent directory!
mkfs.jffs2: skipping device_table entry '/tmp': no parent directory!
mkfs.jffs2: skipping device_table entry '/etc': no parent directory!
-rw-r--r-- 1 root root 7098064 Sep 23 09:47 /usr/arm/buildroot/binaries/at91sam9263ek/rootfs.arm-20080923.jffs2 rm -f /usr/arm/buildroot/project_build_arm/at91sam9263ek/.fakeroot*
Something very strange is going on. Anyone else see this or have any suggestions?
Thanks, Matt.
Signature · 1 line
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
On Wed, 24 Sep 2008 16:05:33 +0200
"Matt Wood" <[email protected]> wrote:
Hi Matt (-;
Quoted 5 lines
Hi, has anyone seen problems booting an AT91SAM9263-EK board with the JFFS2 filesystem created by buildroot? I used to be able to boot no problem with an older version of buildroot, but not with the latest. I'm getting the following kernel panic:
Quoted 8 lines
VFS: Mounted root (jffs2
filesystem). Freeing init memory:
136K Warning: unable to open an initial
console. Kernel panic - not syncing: No init found. Try passing init= option to kernel.I've loaded the NAND flash as follows:
If your NAND flash is properly partitioned in the board code, the layout will show up as the following below.
Quoted 2 lines
0x00000000- at91bootstrap
mtd0
Quoted 2 lines
0x00020000- u-boot
mtd1
Quoted 2 lines
0x00200000- kernel
mtd2
Quoted 2 lines
0x00400000- JFFS2
mtd3
Quoted 3 lines
My bootargs are "mem=64M console=ttyS0,115200 root=/dev/mtdblock1 rw rootfstype=jffs2"
Try root=mtd3, you do not need to specify /dev/mtdblock1.
Quoted 4 lines
The strange thing is if I change the bootargs to root=/dev/mtdblock0, I get a ton of jffs2 oob and ecc errors, but after a while, it gives me the login prompt.
This is just weird, could you post the output from the kernel boot at
http://pastebin.org/ or something similar?
Quoted 5 lines
My JFFS2 memory type options are:
Page Size: 0x800 Erase Block Size: 0x20000Not using clean marker.
These options seems right, 2048 bytes pages and 128 kB erase blocks.
Quoted 9 lines
These options never gave me a problem before.
The only other thing I can think of is a message I get after a build of buildroot about skipping dev, tmp, and etc while creating the RFS:
table='target/device/Atmel/root/device_table.txt' mkfs.jffs2: skipping
device_tableentry '/dev': no parent directory! mkfs.jffs2: skippingdevice_tableentry '/tmp': no parent directory! mkfs.jffs2: skippingdevice_tableentry '/etc': no parent directory!
I see these as well, but they do not impact the generated image.
<snipp>
Signature · 2 lines
Best regards, Hans-Christian Egtvedt