An observation with omap_xload
Sascha Hauer
s.hauer at pengutronix.de
Tue Feb 7 17:27:20 EST 2012
On Tue, Feb 07, 2012 at 05:23:13PM +0000, Premi, Sanjeev wrote:
> Yesterday, i spent quite sometime dealing with 'MLO', unable to find
> 'barebox.bin'. The failure was always:
>
> barebox 2012.01.0ABC-00248-g9119228-dirty (Feb 7 2012 - 16:39:43)
>
> Board: Texas Instrument's OMAP3EVM
> Malloc space: 0x87bfff10 -> 0x87ffff0f (size 4 MB)
> Stack space : 0x4020f000 -> 0x4020fc00 (size 3 kB)
> booting from MMC1
> mounting sd card failed with -22
> booting failed
>
> Since, I was working mostly off the windows machine, i didn't
> realize that SD card had only one partition and mount would
> fail as we explicitly mount "disk0.0" in omap_xload_boot_mmc().
You mean that it only has one partition without a partition table?
>
> Unfortunately, trying to mount "disk0" didn't help and I got
> same error. Haven't debugged this further though.
>
> Also, would it make sense to try mounting "disk0.0" and "disk0"
> before returning failure?
Yes, seems to make sense. The only contra I can imagine is that
for booting a kernel and rootfs the user probably needs a partitioned SD
card anyway.
>
> I am anyways planning to submit a patch changing the message:
> mounting sd card failed with -22
> to
> Unable to mount disk0.0 (-22)
Sounds good.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox
mailing list