Re: U-boot weird MMC boot issue MP30AR0
On Sunday, November 17, 2019 at 2:30:02 AM UTC-8, Michael Howard wrote:
> I have a weird u-boot issue that I have been fighting with for a good
> few days now. It's on the Gigabyte MP30AR0 board and the supplied u-boot
> describes itself as 'U-Boot 2013.04-mp30ar0_sw_1.18.04 (Sep 02 2015 -
> 16:38:06) REV: F06b ( uart0 )', which I'm stuck with I believe.
>
> I'm using a simple 'bootargs', the content of which is
> ''root=/dev/mmcblk0p2 console=ttyS0,115200
> earlycon=uart8250,mmio32,0x1c020000 rootdelay=10''. I've also tried
> variations using UUID.
>
> If I tftpboot the uImage, uInitrd and the dtb to memory (from a tftp
> server, obviously) and then use bootm to boot the system with the rootfs
> on the second partition of the mmc, all is good.
>
> If I fatload the same images, to the same memory locations and boot with
> the same bootm command, the root filesystem, /dev/mmcblk0p2, is not found.
>
> It's got me a bit stumped. Anybody got any ideas of things to try?
>
> Mike.
>
> --
Hi Mike,
Do this before bootm in both cases to see if u-boot recognizes the partition as you'd expect it to:
mmc part
Furthermore, since you are booting with uInitrd, you can use partition label in the bootargs to ensure the kernel will find the rootfs partition successfully (you would need to label the rootfs mmc partition as rootfs first):
root=LABEL=rootfs console=ttyS0,115200 earlycon=uart8250,mmio32,0x1c020000 rootdelay=10
Reply to: