Hi All,
I'm facing with the JFFS2/NAND stuff around AM1808 EVM (w sdk_5.03.02.00).
After having cross-compiled and installed MTD-utilities in my NFS-exported filesystem
I'm able to generate a JFFS2 image and store it in NAND's "rootfs" partition (/dev/mtdblock4).
Some warning messages appear during sector erase:
> flash_erase /dev/mtd4 0 0
Erasing 128 Kibyte @ 14aa0000 -- 65 % complete flash_erase: Skipping bad block at 14ac0000
Erasing 128 Kibyte @ 1f960000 -- 99 % complete flash_erase: Skipping bad block at 1f980000
flash_erase: Skipping bad block at 1f9a0000
flash_erase: Skipping bad block at 1f9c0000
flash_erase: Skipping bad block at 1f9e0000
Erasing 128 Kibyte @ 1f9e0000 -- 100 % complete
Anyway, I proceed with writing
> nandwrite -p /dev/mtd4 rootfs-base-summed.jffs2
Then I can reboot with success..
VFS: Mounted root (jffs2 filesystem) on device 31:4.
OK!
However, for production I think it could be more convenient to fill the NAND flash from u-boot.
And the problem arises when I try to store the same image from within u-boot:
# tftp c2000000 k5/rootfs-base-summed.jffs2
# nand erase.part rootfs
# nand write c2000000 rootfs ${filesize}
Also here, the following messages appear during sector erase:
NAND erase.part: device 0 offset 0x4c0000, size 0x1fb40000
Bad block table found at page 262080, version 0x01
Bad block table found at page 262016, version 0x01
nand_read_bbt: Bad block at 0x0000150c0000
Skipping bad block at 0x150c0000
Skipping bad block at 0x1ff80000
Skipping bad block at 0x1ffa0000
Skipping bad block at 0x1ffc0000
Skipping bad block at 0x1ffe0000
Now try to boot..
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
Can anyone help me?
Gabriele