mkroms.htm

mips架构的bootloader,99左右的版本 但源代码现在没人更新了

		<title>Making ROMS</title>
		<h1 align=center>Making ROMS</h1>

<!--INDEX "Making ROMS" "ROM socket" "PROM Programmer" -->
<!--INDEX ATMizer-1 ATMizer-2 -->

To make a <a href="romdef.htm">ROM</a>, first download the appropriate file 
to your PROM Programmer. The following table shows the location of the
various binaries.<p>

<center><table border cellpadding=5>
<tr><td>
Prom Monitor (PMON)
</td><td>
pmon/bg/pmon.rec (Big endian)<br>
pmon/lg/pmon.rec (Little endian)
</td></tr>

<tr><td>
SerialICE Monitor (IMON)
</td><td>
imon/bg/imon.rec (Big endian)<br>
imon/lg/imon.rec (Little endian)
</td></tr>

<tr><td>
SerialICE Kernels
</td><td>
bsps/k*.rec
</td></tr>

</table></center><p>

Note that you will need to set the device type and split multiple (if
any) before you start the download. A split multiple is necessary if
the Target board requires more than one <a href="romdef.htm">ROM</a>
as a minimum configuration. <p>

Note that if your board requires more than one ROM as a minimum
configuration and is also using the little <a
href="endian.htm">endian</a> byte ordering, the ROMs will need to be
inserted in the reverse order to that used by a big endian processor.
For example, if a board has sockets A, and B, and for big endian,
device 1 from the programmer is inserted in socket A, and device 2 in
socket 2. The reverse will be true for little endian, ie. device 1 will
be inserted in socket B, and device 2 in socket A.<p>

Then set the Programmer's record type to <a href="srec.htm">Motorola
S-records</a>. For some toolsets, you will also need to specify an
offset on the PROM programmer. The offset is required because some
toolsets produce S-records that start at a non-zero address, whereas
most PROM programmers expect the S-records to start at zero.  The
following table shows the offsets required for the various MIPS
toolsets.<p>

<center><table border cellpadding=5>
<tr><th></th><th colspan=3>Offset</th></tr>
<tr><th>
Toolset Vendor Name
</th><th>
ATMizer-1
</th><th>
ATMizer-2
</th><th>
Other MIPS CPUs
</th></tr>

<tr><td>
MIPS
</td><td>
0x00000000
</td><td>
0x00000000
</td><td>
0x00000000
</td></tr>

<tr><td>
EPI
</td><td>
0xa0c00000
</td><td>
0x80000000
</td><td>
0x9fc00000
</td></tr>

<tr><td>
BSO Tasking
</td><td>
0xa0c00000
</td><td>
0x80000000
</td><td>
0x9fc00000
</td></tr>

<tr><td>
Cygnus Support (ECOFF)
</td><td>
0x00000000
</td><td>
0x00000000
</td><td>
0x00000000
</td></tr>

<tr><td>
Cygnus Support (ELF)
</td><td>
0xa0c00000
</td><td>
0x80000000
</td><td>
0x9fc00000
</td></tr>

<tr><td>
Algorithmics
</td><td>
0x00000000
</td><td>
0x00000000
</td><td>
0x00000000
</td></tr>
</table></center><p>

You must make sure that the PROM you are using is large enough to 
hold the program. Unfortunately, most PROM Programmers will not warn 
you if your program is too large. You should be suspicious if the PROM 
Programmer reports that the number of bytes downloaded is exactly the 
same size as your PROM; this generally means that some data is being 
omitted. Note that you cannot simply look at the address in the last 
record of the S-record file, because some toolsets do not emit the 
S-records in order.<p>

If you don't have a PROM programmer, I can personally recommend the
emp20 programmer from
<a href="http://www.needhams.com">Needham's Electronics</a>.
It is inexpensive and connects to the parallel port on a PC.<p>


</dl><p><hr>
<b>Navigation:</b> 
<a href="index.htm">Document Home</a> | 
<a href="doctoc.htm">Document Contents</a> | 
<a href="docindex.htm">Document Index</a> <p>