On 20/05/2011 17:54, wrote Flemming Richter Mikkelsen:
>
> This is as I expect as (as far as I know), uboot does not support ext2/ext3.
> Uboot should find a kernel (uImage.bin) on the first partition (mmcblk0p1) and
> boot that kernel.
>
Ahh okay
>
>
> This is just a wild guess from me, but maybe it should have been:
> menu_1=Boot from microSD (FAT+ext2):
> bootcmd=setenv bootargs rootfstype=ext2 root=/dev/mmcblk0p2
> rootdelay=5 ${mtdparts} ro; mmcinit;
> fatload mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000
>
>
I tried with:
setenv menu_1 Boot from microSD (FAT+ext2): bootcmd=setenv bootargs
rootfstype=ext2 root=/dev/mmcblk0p2 rootdelay=5 ${mtdparts} ro; mmcinit;
fatload mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000
after that the device rebootet straightaway. I did not have the chance
to call saveenv.
After the reboot I got the error unable to mount rootfs on unknown-block
(179,2)
or ... on unknown-block(0,0)
I tried it also with
setenv menu_1 Boot from microSD (FAT+ext2):
setenv bootcmd setenv bootargs rootfstype=ext2 root=/dev/mmcblk0p2
rootdelay=5 ${mtdparts} ro; mmcinit;
fatload mmc 1 0x32000000 ${sd_image_name}; bootm 0x32000000
but this suppose not to be right. rootdelay is also an u-boot-env. So
what is to set on the u-boot and which is to be forwarted to the kernel?
$ are to escaped, if they embedded.
Thank you
Christian
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user
