I have a pogoplug that I would like to update u-boot for the additional features.
To boot from nand my bootargs and bootcmd are:
console=console=ttyS0,115200
bootargs_root=root=/dev/mtdblock2 ro
bootargs_mtdparts=mtdparts=nand_mtd:0x100000@0(u-boot)ro,0x00200000@0x100000(uImage)ro,0x02000000@0x00300000(root)ro,0x1DD00000@0x02300000(data)ro,0x00000033@0x00000200(NAND 16MiB 1,8V 8-bit)ro
bootcmd_nand_mtd=nand read 0x2000000 0x100000 0x200000; setenv bootargs $(console) $(bootargs_root) $(bootargs_mtdparts); bootm 0x2000000
I use
run bootcmd_nand_mtd
to boot.
When I boot this using the pogoplug uboot
http://www.pogoplugged.com/download/11607/ce_uboot_v1.0.bin/ everything works fine.
When I update uboot using the original sheeva uboot:
bubt u-boot-rd88f6281Sheevaplug_400db_nand.bin
and answer n to the question
Override Env parameters? (y/n)
reset and boot as before, the kernel hangs at "done, booting the kernel"
When I bubt the uboot back to the pogoplug image and again do not override the env parameters, the kernel boots again.
The Cloud Engines uboot reports itself as
U-Boot 1.1.4 (Mar 18 2009 - 16:11:55) Cloud Engines (3.4.16)
The Marvell uboot reports itself as:
U-Boot 1.1.4 (Mar 2 2009 - 12:16:00) Marvell version: 3.4.16
I have the mtdparts set up correctly for the pogoplug although mtd3 is not used by pogoplug and mtd4 makes no sense to me but it is what the kernel reports if mtdparts is not defined.
The environment variables are the same, the kernel is the same, the root filesystem is the same, the only thing changed is the uboot image and that even reports itself as the same version.
Anyone have any guesses as to what would cause the kernel to hang?