fatload/ext2load both require that the device and partition be
specified after specifying the device type. Specify the first
partition on mmc device 0, which is the only mmc device currently
configured on the pandora.
Signed-off-by: Vagrant Cascadian <vagr...@debian.org>
---
include/configs/omap3_pandora.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/configs/omap3_pandora.h b/include/configs/omap3_pandora.h
index 380ec12..6ff9375 100644
--- a/include/configs/omap3_pandora.h
+++ b/include/configs/omap3_pandora.h
@@ -93,8 +93,8 @@
"mtdparts=" MTDPARTS_DEFAULT "\0" \
#define CONFIG_BOOTCOMMAND \
- "if mmc rescan && fatload mmc1 0 ${loadaddr} autoboot.scr || " \
- "ext2load mmc1 0 ${loadaddr} autoboot.scr; then " \
+ "if mmc rescan && fatload mmc 0:1 ${loadaddr} autoboot.scr || " \
+ "ext2load mmc 0:1 ${loadaddr} autoboot.scr; then " \
"source ${loadaddr}; " \
"fi; " \
"ubi part boot && ubifsmount ubi:boot && " \
--
2.9.3
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
