using the bootstrap loader
using the bootstrap loader
using the bootstrap loader
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
OVERVIEW OF BOOTSTRAP LOADER OPERATIONS<br />
Remote Third Stage<br />
The remote third stage is similar to <strong>the</strong> generic third stage in that it only runs in real<br />
address mode and can only load applications in <strong>the</strong> first 840K of memory. This third stage<br />
works with <strong>the</strong> iSBC 552A first stage device driver to load <strong>the</strong> operating system from a<br />
remote device <strong>using</strong> <strong>the</strong> E<strong>the</strong>rnet Local Area Network (LAN).<br />
The remote third stage is different from <strong>the</strong> generic third stage in that it is loaded by a<br />
combination of <strong>the</strong> first stage iSBC 552A device driver and <strong>the</strong> firmware executing on <strong>the</strong><br />
iSBC 552A board, not <strong>the</strong> second stage.<br />
Naming <strong>the</strong> Third Stage<br />
Both <strong>the</strong> generic and <strong>the</strong> device-specific third stages are stored as executable files. The<br />
base portion of this file's name -- <strong>the</strong> filename minus any extension -- must be <strong>the</strong> same as<br />
<strong>the</strong> base portion of <strong>the</strong> file containing <strong>the</strong> application system to be loaded. Because <strong>the</strong><br />
name of <strong>the</strong> third stage and <strong>the</strong> name of <strong>the</strong> application system must match, you must<br />
provide a separate third stage file for each bootable system on <strong>the</strong> volume. To provide<br />
additional third stage files, simply make a copy of <strong>the</strong> third stage file you are now <strong>using</strong>.<br />
Name <strong>the</strong> copy so it matches <strong>the</strong> application system you intend to load.<br />
1.2.4 Load File<br />
1-6<br />
The load file is a file containing <strong>the</strong> application system you are booting. The load file<br />
should be on an iRMX 1- or iRMX II-formatted named volume. This volume must have<br />
been formatted by <strong>the</strong> Human Interface FORMAT command. If <strong>the</strong> load file is an iRMX<br />
II application, <strong>the</strong> volume must also have a file containing <strong>the</strong> third stage of <strong>the</strong> Bootstrap<br />
Loader.<br />
If your load file is an iRMX II application, <strong>the</strong> name of that file must correspond to <strong>the</strong><br />
name of <strong>the</strong> Bootstrap Loader third stage, as follows:<br />
• The base portion of <strong>the</strong> load file's name (<strong>the</strong> filename minus <strong>the</strong> extension) must be<br />
<strong>the</strong> same as that of <strong>the</strong> file containing <strong>the</strong> third stage.<br />
• The extension portion of <strong>the</strong> load file's name must consist of <strong>the</strong> characters ".286".<br />
Bootstrap Loader