[U-Boot] beagle bootcmd not set to CONFIG_BOOTCOMMAND in version 2011.03-rc1
Alexander Holler
holler at ahsoftware.de
Mon Mar 7 11:01:55 CET 2011
Hello,
Am 05.03.2011 14:57, schrieb Egon Boormans:
> It looks like the bootcmd doesn't get set to the CONFIG_BOOTCOMMAND value in
> the 'include/configs/omap3_beagle.h' file. This value makes it into the
> 'include/autoconf.mk' file but not into the printenv of the u-boot. If I
...
> NAND: 256 MiB
> MMC: OMAP SD/MMC: 0
> In: serial
> Out: serial
> Err: serial
> Beagle xM Rev A
> No EEPROM on expansion board
> Die ID #6cf600011ff00000015739eb0c00600f
> Hit any key to stop autoboot: 0
> mmc - MMC sub system
>
> Usage:
Looks like you have a Beagle XM with NAND and you've saved the
environment there. Try "env default -f; saveenv" to reset the
environment there to the default values. You could just clean the
environment in the NAND too. For further reference read instructions for
the BeagleBoard (w/o XM), the NAND on some XM doesn't officially exists
and therefor is not mentionend in any documentation for the XM-version.
Regards,
Alexander Holler
More information about the U-Boot
mailing list