From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Holler <holler@ahsoftware.de>
Date: Mon, 07 Mar 2011 11:01:55 +0100
Subject: [U-Boot] beagle bootcmd not set to CONFIG_BOOTCOMMAND in
 version 2011.03-rc1
In-Reply-To: <20110305150034.107B728078@theia.denx.de>
References: <20110305150034.107B728078@theia.denx.de>
Message-ID: <4D74AD13.10806@ahsoftware.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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