[quote="Cyberian"]As far as I remember the pre-built images for Angstrom use another partitioning of the NAND flash.
So you probably have your Angstrom jffs Image copied to 0x2000000 in NAND.
Most newer Kernels use another partitioning scheme in NAND.
0x0 to 0x20000 Bootstrap (/dev/mtdblock0)
0x20000 to 0x60000 U-Boot (/dev/mtdblock1)
0x60000 to 0x80000 U-Boot Env 1 (/dev/mtdblock2)
0x80000 to 0xA0000 U-Boot Env 2 (/dev/mtdblock3)
0xA0000 to 0x2A0000 Linux Kernel (/dev/mtdblock4)
From 0x2A0000 Root file system. (/dev/mtdblock5)
This is the one you also use now specified by the bootargs parameter of U-Boot discussed in another thread.
Take your time and read through
http://www.linux4sam.com, it is worth it.[/quote]
A co-worker and I have been all over the linux4SAM site. We believe we are close, just not understanding where things go.
I ran 'make menuconfig' and told it to make a jffs2 filesystem instead of the .tar. So now the most success is occurring with the following:
1) pre-built (from Linux4SAM website) bootstrap program (0x0 in nandflash)
2) pre-built (from Linux4SAM website) u-boot program (0x20000 in nandflash)
3) buildroot's kernel, named uImage (0xa0000 in nandflash)
4) buildroot's fs, named rootfs.jffs2 (tried it at 0x2a0000 and 0x400000 in nandflash)
This is what we see:
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
List of all partitions:
1f00 4096 mtdblock0 (driver?)
1f01 61440 mtdblock1 (driver?)
1f02 196608 mtdblock2 (driver?)
No filesystem could mount root, tried: jffs2
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
[<c002d5dc>] (unwind_backtrace+0x0/0xdc) from [<c02588a4>] (panic+0x34/0x120)
[<c02588a4>] (panic+0x34/0x120) from [<c0008f18>] (mount_block_root+0x1d4/0x21c)
[<c0008f18>] (mount_block_root+0x1d4/0x21c) from [<c00091c8>] (prepare_namespace
+0x164/0x1c8)
[<c00091c8>] (prepare_namespace+0x164/0x1c8) from [<c0008444>] (kernel_init+0xd8
/0x110)
[<c0008444>] (kernel_init+0xd8/0x110) from [<c0028e1c>] (kernel_thread_exit+0x0/
0x8)
INFO: RCU detected CPU 0 stall (t=1000 jiffies)
INFO: RCU detected CPU 0 stall (t=4000 jiffies)
We are really confused about the setting of the mtd blocks? We've read we set it in kernel config, but we don't see any menuconfig option to do so. We've tried the uboot argument bootargs with root=/dev/mtdblock1 and root=/dev/mtdblock5.
Can you help clear this up for us? We have been reading a lot on Linux4SAM and feel we are close.
Forum
