doc101.htm

Reh Hat user manual. really goooood

<p><blockquote><font size=-1><tt>
<pre>
        &gt;&gt;&gt;boot dva0
        (boot dva0.0.0.0.1 -flags 0)
        block 0 of dva0.0.0.0.1 is a valid boot block
        reading 621 blocks from dva0.0.0.0.1
        bootstrap code read in
        base = 112000, image_start = 0, image_bytes = 4da00
        initializing HWRPB at 2000
        initializing page table at 104000
        initializing machine state
        setting affinity to the primary CPU
        jumping to bootstrap code
        MILO Stub: V1.1
        Unzipping MILO into position
        Allocating memory for unzip
        ####...
</pre>
</tt></font></blockquote>

<p>The following systems are <em>known</em> to have SRM Console support:
<ul>
<li>Noname (Section <a href="doc101.html#sD.5.7.1">D.5.7.1</a>)
<li>AlphaPC64 (Section <a href="doc101.html#sD.5.7.2">D.5.7.2</a>)
<li>EB164 (Section <a href="doc101.html#sD.5.7.6">D.5.7.6</a>)
<li>PC164 (Section <a href="doc101.html#sD.5.7.7">D.5.7.7</a>)
</ul>

<p><h3><a name="sD.5.7">D.5.7 System Specific Information</a></h3>
<title>System Specific Information</title>


<p><h4><a name="sD.5.7.1">D.5.7.1 AxpPCI33 (Noname)</a></h4>
<title>AxpPCI33 (Noname)</title>


<p>The Noname board can load MILO 
from the Windows NT ARC firmware
(Section <a href="doc101.html#sD.5.1">D.5.1</a>),
from the SRM Console
(Section <b><font size=+1>??</font></b>).
and from a failsafe boot block floppy
(Section <a href="doc101.html#sD.5.4">D.5.4</a>).
A flash management utility, runnable from MILO is available so that
once MILO is running, it can be blown into flash
(Section <a href="doc103.html#sD.7">D.7</a>).
However, be warned
that once you have done this you will lose the previous image held there
as there is only room for one image.

<p>The way that Noname boots is controlled
by a set of jumpers on the board, J29 and J28.  These look like:
<blockquote><font size=-1><tt>
<pre>
                    4
        J29     2 x x x 6
                1 x x x 5

        J28     2 x x x 6
                1 x x x 5
                    3
</pre>
</tt></font></blockquote>

<p>The two options that we're interested in are J28, pins 1-3 which
boots the console/loader from flash and J29, pins 1-3 which boots the
console/loader from a boot block floppy.  The second option is the one
that you need to first boot MILO on the Noname board.

<p>Once you've selected the boot from floppy option via the jumpers,
put the SRM boot block floppy containing MILO into the
floppy and reboot.  In a few seconds (after the floppy light goes out)
you should see the screen blank to white and MILO telling
you what's going on.

<p>If you are really interested in technical stuff, the Noname loads
images off of the floppy into physical address 0x104000 and images
from flash into 0x100000.  For this reason, MILO is built
with it's PALcode starting at 0x200000.  When it is first loaded, it
moves itself to the correct location (see relocate.S).

<p><h4><a name="sD.5.7.2">D.5.7.2 AlphaPC64 (Cabriolet)</a></h4>
<title>AlphaPC64 (Cabriolet)</title>


<p>The AlphaPC64 includes the Windows NT ARC firmware
(Section <a href="doc101.html#sD.5.1">D.5.1</a>),
the SRM Console (Section <b><font size=+1>??</font></b>)
and the Evaluation Debug Monitor 
(Section <a href="doc101.html#sD.5.3">D.5.3</a>).
These images are in flash and there is room to add MILO so that
you can boot MILO directly from flash.
A flash management utility, runnable from MILO is available so that
once MILO is running, it can be blown into flash
(Section <a href="doc103.html#sD.7">D.7</a>).
This system supports MILO environment variables.

<p>You select between the boot options (and MILO when it is
been put into flash) using a combination of jumpers and a boot option which
is saved in the NVRAM of the TOY clock.

<p>The jumper is J2, SP bits 6 and 7 have the following meanings:
<ul>
<li>SP bit 6 should always be out.  If this jumper is set then the
SROM mini-debugger gets booted,
<li>SP bit 7 in is boot image selected by the boot option byte in 
the TOY clock,
<li>SP bit 7 out is boot first image in flash.
</ul>

<p>So, with bit 7 out, the Debug Monitor will be booted as it is <tt>always</tt>
the first image in flash.  With bit 7 in, the image selected by
the boot option in the TOY clock will be selected.  
The Debug Monitor, the Windows NT ARC firmware and MILO all support setting
this boot option byte but you must be very careful using it.
In particular, you cannot set the boot option so that next time the system
boots MILO when you are running the Windows NT ARC firmware, it only
allows you to set Debug Monitor or Windows NT ARC as boot options.

<p> To get MILO into flash via the Evaluation Board Debug Monitor, 
you will need a flashable image.
The build proceedures make MILO.rom, 
but you can also make a rom image using the makerom tool in the 
Debug Monitor software that comes with the board:

<p><pre>
    &gt; makerom -v -i7 -l200000 MILO -o mini.flash
</pre>

<p> (type makerom to find out what the arguments mean, but 7 is a
flash image id used by the srom and -l200000 gives the load address
for the image as 0x200000).

<p>Load that image into memory (via the Debug Monitor commands flload,
netload, and so on) at 0x200000 and then blow the image into flash:

<p><blockquote><font size=-1><tt>
<pre>
     AlphaPC64&gt; flash 200000 8
</pre>
</tt></font></blockquote>

<p> (200000 is where the image to be blown is in memory and 8 is the segment
number where you put the image.   There are 16 1024*64 byte segments in the
flash and the Debug Monitor is at seg 0 and the Windows NT ARC firmware is at seg 4).

<p> Set up the image that the srom will boot by writing the number of
the image into the TOY clock.

<p><blockquote><font size=-1><tt>
<pre>
     AlphaPC64&gt; bootopt 131
</pre>
</tt></font></blockquote>

<p>(131 means boot the 3rd image, 129 = 1st, 130 = 2nd and so on).

<p> Power off, put jumper 7 on and power on and you should see the
MILO burst into life.  If you don't then take jumper 7 back off
and reboot the Debug Monitor.

<p><h4><a name="sD.5.7.3">D.5.7.3 EB66+</a></h4>
<title>EB66+</title>


<p>The EB66+, like all of the Alpha Evaluation Boards built by Digital
contains the Evaluation Board Debug Monitor and so this is available
to load MILO
(Section <a href="doc101.html#sD.5.3">D.5.3</a>).  
Quite often (although not always) boards whose design is derived from
these include the Debug Monitor also.
Usually, these boards include the Windows NT ARC firmware
(Section <a href="doc101.html#sD.5.1">D.5.1</a>).
A flash management utility, runnable from MILO is available so that
once MILO is running, it can be blown into flash
(Section <a href="doc103.html#sD.7">D.7</a>).
This system supports MILO environment variables.

<p>These systems have several boot images in flash controlled by jumpers.  
The two jumper banks are J18 and J16 and are located at the bottom
of the board in the middle (if the Alpha chip is at the top).
You select between the boot options (and MILO when it is
been put into flash) using a combination of jumpers and a boot option which
is saved in the NVRAM of the TOY clock.

<p>Jumper 7-8 of J18 in means boot the image described by the
boot option.   Jumper 7-8 of J18 out means boot the Evaluation Board
Debug Monitor.

<p>Blowing an image into flash via the Evaluation Board Debug Monitor
is exactly the same proceedure as
for the AlphaPC64 (Section <a href="doc101.html#sD.5.7.2">D.5.7.2</a>).

<p><h4><a name="sD.5.7.4">D.5.7.4 EB64+/Aspen Alpine</a></h4>
<title>EB64+/Aspen Alpine</title>


<p>This system is quite like the AlphaPC64 except that it does not
contain flash which MILO can be loaded from.
The EB64+ has two ROMs, one of which contains
the Windows NT ARC firmware
(Section <a href="doc101.html#sD.5.1">D.5.1</a>).  
and the other contains the Evaluation Board Debug Monitor 
(Section <a href="doc101.html#sD.5.3">D.5.3</a>).  

<p>The Aspen Alpine is a little different in that it only has one
ROM; this contains the Windows NT ARC firmware.

<p><h4><a name="sD.5.7.5">D.5.7.5 Universal Desktop Box (Multia)</a></h4>
<title>Universal Desktop Box (Multia)</title>


<p>This is a very compact pre-packaged 21066 based system that 
includes a TGA (21030) graphics device.   Although you can <em>just</em> fit
a half height PCI graphics card in the box you are better off waiting
for full TGA support in XFree86.   It includes the Windows NT ARC
firmware and so booting from that is the prefered method
(Section <a href="doc101.html#sD.5.1">D.5.1</a>).

<p><h4><a name="sD.5.7.6">D.5.7.6 EB164</a></h4>
<title>EB164</title>


<p>The EB164, like all of the Alpha Evaluation Boards built by Digital
contains the Evaluation Board Debug Monitor and so this is available
to load MILO
(Section <a href="doc101.html#sD.5.3">D.5.3</a>).  
Quite often (although not always) boards whose design is derived from
these include the Debug Monitor also.
Usually, these boards include the Windows NT ARC firmware
(Section <a href="doc101.html#sD.5.1">D.5.1</a>).
The SRM console is also available
(Section <b><font size=+1>??</font></b>).
A flash management utility, runnable from MILO is available so that
once MILO is running, it can be blown into flash
(Section <a href="doc103.html#sD.7">D.7</a>).
This system supports MILO environment variables.

<p>These systems have several boot images in flash controlled by jumpers.  
The two jumper bank is J1 and is located at the bottom
of the board on the left (if the Alpha chip is at the top).
You select between the boot options (and MILO when it is
been put into flash) using a combination of jumpers and a boot option which
is saved in the NVRAM of the TOY clock.

<p>Jumper SP-11 of J1 in means boot the image described by the
boot option.   Jumper SP-11 of J1 out means boot the Evaluation Board
Debug Monitor.

<p>Blowing an image into flash via the Evaluation Board Debug
Monitor is exactly the same proceedure as
for the AlphaPC64 (Section <a href="doc101.html#sD.5.7.2">D.5.7.2</a>).

<p><h4><a name="sD.5.7.7">D.5.7.7 PC164</a></h4>
<title>PC164</title>


<p>The PC164, like all of the Alpha Evaluation Boards built by Digital
contains the Evaluation Board Debug Monitor and so this is available
to load MILO
(Section <a href="doc101.html#sD.5.3">D.5.3</a>).  
Quite often (although not always) boards whose design is derived from
these include the Debug Monitor also.
Usually, these boards include the Windows NT ARC firmware
(Section <a href="doc101.html#sD.5.1">D.5.1</a>).
The SRM console is also available
(Section <b><font size=+1>??</font></b>).
A flash management utility, runnable from MILO is available so that
once MILO is running, it can be blown into flash
(Section <a href="doc103.html#sD.7">D.7</a>).
This system supports MILO environment variables.

<p>These systems have several boot images in flash controlled by jumpers.  
The main jumper block, J30, contains the system configuration jumpers and
jumper CF6 in means that the system will boot the Debug Monitor, the default
is out.

<p>Blowing an image into flash via the Evaluation Board Debug
Monitor is exactly the same proceedure as
for the AlphaPC64 (Section <a href="doc101.html#sD.5.7.2">D.5.7.2</a>).

<p><h4><a name="sD.5.7.8">D.5.7.8 XL266</a></h4>
<title>XL266</title>


<p>The XL266 is one of a family of systems that are known as Avanti.  
It has a riser card containing the Alpha chip and cache which plugs into 
the main board at right angles.   This board can replace the equivalent 
Pentium board.

<p>Some of these systems ship with the SRM console but others, notably
the XL266 ship with only the Windows NT ARC firmware
(Section <a href="doc101.html#sD.5.1">D.5.1</a>).

<p>Here is my list of compatible systems:
<ul>
<li>AlphaStation 400 (Avanti),
<li>AlphaStation 250,
<li>AlphaStation 200 (Mustang),
<li>XL.  There are two flavours, XL266 and XL233 with the only
difference being in processor speed and cache size.
</ul>

<p><b>Note</b> The system that I use to develop and test MILO is
an XL266 and so this is the only one that I can guarentee will work.
However, technically, all of the above systems are equivalent; they
have the same support chipsets and the same interrupt handling
mechanisms.

<p><h4><a name="sD.5.7.9">D.5.7.9 Platform2000</a></h4>
<title>Platform2000</title>


<p>This is a 233Mhz 21066 based system.

<p><p><hr>
<a href="doc102.html"><img src=../icons/next.gif alt="Next"></a>
<a href="doc000.html"><img src=../icons/up.gif alt="Up"></a>
<a href="doc100.html"><img src=../icons/previous.gif alt="Previous"></a>
<a href="doc000.html"><img src=../icons/contents.gif alt="Contents"></a>
<a href="doc123.html"><img src=../icons/index.gif alt="Index"></a>
<hr>
</body></html>