1
1
<!-- retain these comments for translator revision tracking -->
2
<!-- original version: 36639 untranslated -->
2
<!-- original version: 62875 untranslated -->
4
4
<sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title>
6
6
&boot-installer-intro-net.xml;
8
<sect3 arch="arm"><title>Booting from TFTP on Netwinder</title>
11
Netwinders have two network interfaces: A 10Mbps NE2000-compatible
12
card (which is generally referred to as <literal>eth0</literal>) and
13
a 100Mbps Tulip card. There may be problems loading the image via TFTP
14
using the 100Mbps card so it is recommended that you use the 10Mbps
15
interface (the one labeled with <literal>10 Base-T</literal>).
20
You need NeTTrom 2.2.1 or later to boot the installation system, and
21
version 2.3.3 is recommended. Unfortunately, firmware files are currently
22
not available for download because of license issues. If this situation
23
changes, you may find new images at <ulink url="http//www.netwinder.org/"></ulink>.
28
When you boot your Netwinder you have to interrupt the boot process during the
29
countdown. This allows you to set a number of firmware settings needed in
30
order to boot the installer. First of all, start by loading the default
33
<informalexample><screen>
34
NeTTrom command-> load-defaults
35
</screen></informalexample>
37
Furthermore, you must configure the network, either with a static address:
39
<informalexample><screen>
40
NeTTrom command-> setenv netconfig_eth0 flash
41
NeTTrom command-> setenv eth0_ip 192.168.0.10/24
42
</screen></informalexample>
44
where 24 is the number of set bits in the netmask, or a dynamic address:
46
<informalexample><screen>
47
NeTTrom command-> setenv netconfig_eth0 dhcp
48
</screen></informalexample>
50
You may also need to configure the <userinput>route1</userinput>
51
settings if the TFTP server is not on the local subnet.
53
Following these settings, you have to specify the TFTP server and the
54
location of the image. You can then store your settings to flash.
56
<informalexample><screen>
57
NeTTrom command-> setenv kerntftpserver 192.168.0.1
58
NeTTrom command-> setenv kerntftpfile boot.img
59
NeTTrom command-> save-all
60
</screen></informalexample>
62
Now you have to tell the firmware that the TFTP image should be booted:
64
<informalexample><screen>
65
NeTTrom command-> setenv kernconfig tftp
66
NeTTrom command-> setenv rootdev /dev/ram
67
</screen></informalexample>
69
If you use a serial console to install your Netwinder, you need to add the
72
<informalexample><screen>
73
NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200
74
</screen></informalexample>
76
Alternatively, for installations using a keyboard and monitor you have to
79
<informalexample><screen>
80
NeTTrom command-> setenv cmdappend root=/dev/ram
81
</screen></informalexample>
83
You can use the <command>printenv</command> command to review your
84
environment settings. After you have verified that the settings are
85
correct, you can load the image:
87
<informalexample><screen>
88
NeTTrom command-> boot
89
</screen></informalexample>
91
In case you run into any problems, a <ulink
92
url="http://www.netwinder.org/howto/Firmware-HOWTO.html">detailed
93
HOWTO</ulink> is available.
98
<sect3 arch="arm"><title>Booting from TFTP on CATS</title>
101
On CATS machines, use <command>boot de0:</command> or similar at the
116
<sect3 arch="arm" id="boot-firmware-ss4000e">
117
<title>Booting the SS4000-E</title>
120
Due to limitations in the SS4000-E firmware, it unfortunately is not
121
possible to boot the installer without the use of a serial port at
122
this time. To boot the installer, you will need a serial nullmodem
123
cable; a computer with a serial port<footnote id="arm-s4ke-port">
126
A USB serial converter will also work.
129
</footnote>; and a ribbon cable with a male DB9 connector at one end,
130
and a 10-pin .1" IDC header at the other<footnote id="arm-s4k-rib">
133
This cable is often found in older desktop machines with builtin 9-pin
141
To boot the SS4000-E, use your serial nullmodem cable and the ribbon
142
cable to connect to the serial port of the SS4000-E, and reboot the
143
machine. You need to use a serial terminal application to communicate
144
with the machine; a good option on a Debian GNU/Linux is to use the
145
<command>cu</command> program, in the package of the same name. Assuming
146
the serial port on your computer is to be found on
147
<filename>/dev/ttyS0</filename>, use the following command line:
151
<informalexample><screen>
153
</screen></informalexample>
157
If using Windows, you may want to consider using the program
158
<classname>hyperterminal</classname>. Use a baud rate of 115200,
159
8 bits word length, no stop bits, and one parity bit.
163
When the machine boots, you will see the following line of output:
167
<informalexample><screen>
168
No network interfaces found
170
EM-7210 ver.T04 2005-12-12 (For ver.AA)
171
== Executing boot script in 1.000 seconds - enter ^C to abort
172
</screen></informalexample>
176
At this point, hit Control-C to interrupt the boot
177
loader<footnote id="arm-s4ke-sec">
180
Note that you have only one second to do so; if you miss this window,
181
just powercycle the machine and try again.
184
</footnote>. This will give you the RedBoot prompt. Enter the
187
<informalexample><screen>
188
load -v -r -b 0x01800000 -m ymodem ramdisk.gz
189
load -v -r -b 0x01008000 -m ymodem zImage
190
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
191
</screen></informalexample>
195
After every <command>load</command> command, the system will expect a
196
file to be transmitted using the YMODEM protocol. When using cu, make
197
sure you have the package <classname>lrzsz</classname> installed, then
198
hit enter, followed by the <quote>~<</quote> escape sequence to start
199
an external program, and run <command>sb initrd.gz</command> or
200
<command>sb vmlinuz</command>.
204
Alternatively, it is possible to load the kernel and ramdisk using
205
HTTP rather than YMODEM. This is faster, but requires a working HTTP
206
server on the network. To do so, first switch the bootloader to RAM mode:
208
<informalexample><screen>
211
</screen></informalexample>
215
This will seemingly restart the machine; but in reality, it loads
216
reboot to RAM and restarts it from there. Not doing this step will cause
217
the system to hang in the necessary ip_address step that comes next.
221
You will need to hit Ctrl-C again to interrupt the boot. Then:
223
<informalexample><screen>
224
ip_address -l 192.168.2.249 -h 192.168.2.4
225
load -v -r -b 0x01800000 -m http /initrd.gz
226
load -v -r -b 0x01008000 -m http /zImage
227
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
228
</screen></informalexample>
232
The installer will now start as usual.