From: Joe Steeve <joe@sliceware.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] environment problem with new board
Date: Wed, 22 Nov 2006 09:31:10 +0530 [thread overview]
Message-ID: <4563CB86.1060006@sliceware.com> (raw)
I'm porting u-boot to a Sigma Designs em8620L based board. The em8620L
is an SOC with an ARMv4t core (pT-110).
I managed to get u-boot to the prompt :) However., a 'printenv' dumps
garbage on the console. I've been slightly clueless as to where to look
in the sources. Any pointers would be of help. I'm defining
'CFG_ENV_IS_NOWHERE'.
I also have defined CONFIG_COMMANDS to CFG_CMD_ALL., however I see only
the following commands when i issue a 'help' on the prompt.,
? - alias for 'help'
bootm - boot application image from memory
go - start application at address 'addr'
help - print online help
printenv- print environment variables
reset - Perform RESET of the CPU
saveenv - save environment variables to persistent storage
setenv - set environment variables
version - print monitor version
Is this right??
--
Joe Steeve
Sliceware Private Limited
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: OpenPGP digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20061122/842a5bbe/attachment.pgp
next reply other threads:[~2006-11-22 4:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 4:01 Joe Steeve [this message]
2006-11-22 8:34 ` [U-Boot-Users] environment problem with new board Wolfgang Denk
2006-11-22 14:08 ` Joe Steeve
2006-11-22 17:58 ` Wolfgang Denk
2006-11-22 19:07 ` Joe Steeve
2006-11-22 20:04 ` Wolfgang Denk
2006-11-23 0:23 ` [U-Boot-Users] PCI Initialization for AMCC440EP Pras
2006-11-23 1:41 ` Wolfgang Denk
2006-11-23 1:10 ` [U-Boot-Users] environment problem with new board Joe Steeve
2006-11-23 1:16 ` Joe Steeve
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=4563CB86.1060006@sliceware.com \
--to=joe@sliceware.com \
--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