From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] beagle bootcmd not set to CONFIG_BOOTCOMMAND in version 2011.03-rc1
Date: Mon, 07 Mar 2011 11:01:55 +0100 [thread overview]
Message-ID: <4D74AD13.10806@ahsoftware.de> (raw)
In-Reply-To: <20110305150034.107B728078@theia.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
next prev parent reply other threads:[~2011-03-07 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 13:57 [U-Boot] beagle bootcmd not set to CONFIG_BOOTCOMMAND in version 2011.03-rc1 Egon Boormans
2011-03-07 10:01 ` Alexander Holler [this message]
2011-03-16 18:10 ` [U-Boot] beagle bootcmd not set to CONFIG_BOOTCOMMAND in version2011.03-rc1 Egon Boormans
2011-03-17 0:11 ` Alexander Holler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D74AD13.10806@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox