Filter
Top Products
HighWire HW400c/2 User Reference Guide Rev 1.0
5.5.1.2 U-boot environment variables
riables and commands. While most can
be used with the HW400c/2, only a few are necessary for the boot process. A
complete list of U-boot environment variables can be found in Appendix B .
Lis
s
eed only be separated by a space (see Section
for
the Linux kernel. Console tty is
e con rg, most of the Linux boot messages will not be displayed.
. bootarg lines of around 250 characters can be executed, however, storing the bootargs in flash
mite l
SBE Technical S
If bootp is used, get the IP
address from there. Other
pply. See section
r setting static IP
addresses
.
ultiple
followed by a space,
e semi colon must be backslash escaped or the second command will not be recorded. Example;
# set bootcmd tftpboot\; bootm
bootdelay The delay time in seconds until autoboot (executes bootcmd)
begins. A countdown is displayed on the command line. Any
U-boot has large number of environment va
t of basic boot variables:
bootarg Boot arguments. Arguments passed to the kernel. Configures the
HW400c/2 console (debug) port for the Linux kernel, the location of
the IP address, if not static, the NFS device, and the NFS root path.
Multiple bootargs n
5.5.2.1). Sample bootargs;
console=ttyMM0,9600n8 Console port configuration
ttyMM0, 9600 baud, 8 bits, no
parity.
sole boota1. Without th
2
memory is li d to 80 characters. See Table 10. If you need extra room for bootargs, please cal
upport.
ip=bootp
settings a
5.5.2.2 fo
nfsroot=/opt/gentoo NFS root file path
root=/dev/nfs rw NFS root device.
The name of the bootfile, e.g. uImage bootfile
bootcmd Boot commands executed during automatic boot (autoboot). M
commands must be separated by a semi colon
followed by the next command.
Th
October 10, 2006 Copyright 2006, SBE, Inc. Page 77