1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
|
<!-- retain these comments for translator revision tracking -->
<!-- $Id$ -->
<sect2 arch="arm" id="boot-tftp"><title>Booting from TFTP</title>
&boot-installer-intro-net.xml;
</sect2>
<sect2 arch="arm"><title>Booting from CD-ROM</title>
&boot-installer-intro-cd.xml;
</sect2>
<sect2 arch="arm" id="boot-firmware"><title>Booting from Firmware</title>
&boot-installer-intro-firmware.xml;
<sect3 arch="arm" id="boot-firmware-ss4000e">
<title>Booting the SS4000-E</title>
<para>
Due to limitations in the SS4000-E firmware, it unfortunately is not
possible to boot the installer without the use of a serial port at
this time. To boot the installer, you will need a serial nullmodem
cable; a computer with a serial port<footnote id="arm-s4ke-port">
<para>
A USB serial converter will also work.
</para>
</footnote>; and a ribbon cable with a male DB9 connector at one end,
and a 10-pin .1" IDC header at the other<footnote id="arm-s4k-rib">
<para>
This cable is often found in older desktop machines with builtin 9-pin
serial ports.
</para>
</footnote>.
</para><para>
To boot the SS4000-E, use your serial nullmodem cable and the ribbon
cable to connect to the serial port of the SS4000-E, and reboot the
machine. You need to use a serial terminal application to communicate
with the machine; a good option on a &debian; GNU/Linux is to use the
<command>cu</command> program, in the package of the same name. Assuming
the serial port on your computer is to be found on
<filename>/dev/ttyS0</filename>, use the following command line:
</para>
<informalexample><screen>
cu -lttyS0 -s115200
</screen></informalexample>
<para>
If using Windows, you may want to consider using the program
<classname>hyperterminal</classname>. Use a baud rate of 115200,
8 bits word length, no stop bits, and one parity bit.
</para><para>
When the machine boots, you will see the following line of output:
</para>
<informalexample><screen>
No network interfaces found
EM-7210 ver.T04 2005-12-12 (For ver.AA)
== Executing boot script in 1.000 seconds - enter ^C to abort
</screen></informalexample>
<para>
At this point, hit Control-C to interrupt the boot
loader<footnote id="arm-s4ke-sec">
<para>
Note that you have only one second to do so; if you miss this window,
just powercycle the machine and try again.
</para>
</footnote>. This will give you the RedBoot prompt. Enter the
following commands:
<informalexample><screen>
load -v -r -b 0x01800000 -m ymodem ramdisk.gz
load -v -r -b 0x01008000 -m ymodem zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
</screen></informalexample>
</para><para>
After every <command>load</command> command, the system will expect a
file to be transmitted using the YMODEM protocol. When using cu, make
sure you have the package <classname>lrzsz</classname> installed, then
hit enter, followed by the <quote>~<</quote> escape sequence to start
an external program, and run <command>sb initrd.gz</command> or
<command>sb vmlinuz</command>.
</para><para>
Alternatively, it is possible to load the kernel and ramdisk using
HTTP rather than YMODEM. This is faster, but requires a working HTTP
server on the network. To do so, first switch the bootloader to RAM mode:
<informalexample><screen>
fis load rammode
g
</screen></informalexample>
</para><para>
This will seemingly restart the machine; but in reality, it loads
redboot to RAM and restarts it from there. Not doing this step will cause
the system to hang in the necessary ip_address step that comes next.
</para><para>
You will need to hit Ctrl-C again to interrupt the boot. Then:
<informalexample><screen>
ip_address -l <replaceable>192.168.2.249</replaceable> -h <replaceable>192.168.2.4</replaceable>
load -v -r -b 0x01800000 -m http /initrd.gz
load -v -r -b 0x01008000 -m http /zImage
exec -c "console=ttyS0,115200 rw root=/dev/ram mem=256M@0xa0000000" -r 0x01800000
</screen></informalexample>
Where <replaceable>192.168.2.249</replaceable> is the IP address of the
installed system and <replaceable>192.168.2.4</replaceable> the IP address
of the HTTP server containing the kernel and ramdisk files.
</para><para>
The installer will now start as usual.
</para>
</sect3>
</sect2>
|
