using the bootstrap loader

More documents

Recommendations

Info

1.1 INTRODUCTION OVERVIEW OF BOOTSTRAP 1 LOADER OPERATIONS The iRMX® Bootstrap Loader is a program that loads your custom version of the iRMX Operating System, known as an application system, into RAM from secondary storage so it can begin running. This process is called bootstrap loading or booting. Booting can occur when the system is turned on, when the system is reset, or under operator control when the monitor is active. Since it's not dependent on any particular operating system, the iRMX Bootstrap Loader can load many different operating systems. The Bootstrap Loader eliminates the need to place complete applications into PROM devices. Instead, you can place the Bootstrap Loader--a small program--into PROM devices and store your application system on a mass storage device. The Bootstrap Loader can then be used to load the application program into RAM. The Bootstrap Loader consists of a series of stages and is necessary for loading iRMX applications. The first stage is located in PROM devices. It determines the name of the file to load, loads part of the second stage, and passes control to that part. Intel 300 Series Microcomputers are delivered with the first stage of the iRMX Bootstrap Loader and the iSDM N monitor already placed in PROM devices. If you are building your own MUL TIBUS® I microcomputer systems, you can use the information in this manual to configure a first stage and place it into PROM devices. Intel System 520 Series Microcomputers are delivered with firmware containing a different Bootstrap Loader than the one described in this manual. None of the information contained in this manual applies to the System 520's Bootstrap Loader. That loader, the MULTIBUS II Systems Architecture (MSA) Bootstrap Loader, is described in the MSA Bootstrap Loading of the System 520 Manual. The second stage is on track 0 of every iRMX-formatted named volume and is necessary for leading iRMX I and iRMX II applications. That is, whenever you use the Human Interface FORMAT command to format a volume, the second stage is copied to that volume. When invoked, the second stage finishes loading itself into memory. Then it loads a file from the same volume and passes control to it. This second stage does not function in the MSA environment. Refer to the MSA Bootstrap Loading of the System 520 Manual for more information. Bootstrap Loader 1-1
OVERVIEW OF BOOTSTRAP LOADER OPERATIONS 1-2 The contents of this load file depend on the type of system you are loading. If you are loading an iRMX I system, the file loaded by the second stage contains the application system itself. If you are loading an iRMX II system, the file loaded by the second stage contains the third stage of the Bootstrap Loader, which finishes the loading process. The third stage is necessary only for loading iRMX II applications, because these applications require the 80286/3861\1 processor to be running in protected mode and because they use the OMF-286 object module format. The OMF-286 format is different from the OMF-86 format and therefore cannot be handled by the second stage. The third stage places the processor in protected mode, loads the iRMX II application system, and transfers control to that application system. The third stage is in a named file on the same volume as the second stage. Your Bootstrap Loader package contains a configured third stage that can load applications from selected devices. The instructions in this manual can help you configure your own third stage to add support for other devices. The bootstrap loading process cannot be accomplished without a device driver. The device driver is a small program that provides the interface between the Bootstrap Loader and a device controller. When you configure the Bootstrap Loader (a task that is independent of iRMX Operating System configuration), you specify the device drivers that the Bootstrap Loader requires. During configuration, these device drivers, which are distinct from the drivers needed by the application system, are linked to the Bootstrap Loader. Bootstrap Loader
Page 2: iRMX® Bootstrap loader Reference M
Page 5 and 6: I \
Page 7 and 8: PREFACE Appendix B This appendix de
Page 9 and 10: Contents Chapter 3. Configuring the
Page 11 and 12: Contents Chapter 6. Writing a Custo
Page 16 and 17: 1.2 THE STAGES OF THE BOOTSTRAP LOA
Page 18 and 19: Generic Third Stage OVERVIEW OF BOO
Page 20 and 21: OVERVIEW OF BOOTSTRAP LOADER OPERAT
Page 22 and 23: * OVERVIEW OF BOOTSTRAP LOADER OPER
Page 24: OVERVIEW OF BOOTSTRAP LOADER OPERAT
Page 27 and 28: USING THE BOOTSTRAP LOADER 2-2 When
Page 29 and 30: USING THE BOOTSTRAP LOADER 2-4 For
Page 31 and 32: USING THE BOOTSTRAP LOADER 2-6 Alth
Page 33 and 34: USING THE BOOTSTRAP LOADER * 2-8 NO
Page 35 and 36: CONFIGURING THE FIRST STAGE 3.1.1 F
Page 37 and 38: CONFIGURING THE FIRST STAGE 3-4 nam
Page 39: CONFIGURING THE FIRST STAGE 3-6 , ,
Page 42 and 43: CONFIGURING THE FIRST STAGE The ord
Page 44 and 45: CONFIGURING THE FIRST STAGE 3.2.3 %
Page 46 and 47: where: mpc$base$addr port$sep duty$
Page 48 and 49: 3.2.7 %CONSOLE, %MANUAL, and %AUTO
Page 50 and 51: CONFIGURING THE FIRST STAGE • If
Page 52 and 53: The syntax of this macro is %CLEAR
Page 54 and 55: The syntax of the %SERIAL _ CHANNEL
Page 56 and 57: CONFIGURING THE FIRST STAGE flags A
Page 58 and 59: The syntax of the %DEVICE macro is
Page 60 and 61: CONFIGURING THE FIRST STAGE Table 3
Page 62 and 63: 3.3 BSERR.A86 CONFIGURATION FILE CO
Page 64 and 65:
3.3.4 %AGAIN Macro CONFIGURING THE
Page 66 and 67:
3.4 DEVICE DRIVER CONFIGURATION FIL
Page 68 and 69:
In the BMSC.A86 file, the default i
Page 71 and 72:
CONFIGURING THE FIRST STAGE 3.4.6 %
Page 73 and 74:
CONFIGURING THE FIRST STAGE def cla
Page 75 and 76:
CONFIGURING THE FIRST STAGE In the
Page 77 and 78:
CONFIGURING THE FIRST STAGE 3.4.11
Page 79 and 80:
CONFIGURING THE FIRST STAGE 3-46 Mu
Page 82:
The format for invoking the submit
Page 85 and 86:
CONFIGURING THE THIRD STAGE 4.2 OVE
Page 87 and 88:
CONFIGURING THE THIRD STAGE 4.3 BS3
Page 89 and 90:
CONFIGURING THE THIRD STAGE name bs
Page 91 and 92:
CONFIGURING THE THIRD STAGE 4.3.1 %
Page 93 and 94:
CONFIGURING THE THIRD STAGE Table 4
Page 95:
CONFIGURING THE THIRD STAGE The def
Page 98 and 99:
CONFIGURING THE THIRD STAGE This ma
Page 100 and 101:
attachfile bsl as :fl: asm86 bg3.a8
Page 102 and 103:
Generic third stage where: SUBMIT B
Page 104 and 105:
5.1 INTRODUCTION 5 WRITING A CUSTOM
Page 106 and 107:
5.2 DEVICE INITIALIZE PROCEDURE WRI
Page 108 and 109:
Adding the following statements acc
Page 110 and 111:
", ", """""", " " , " " "", " """""
Page 112 and 113:
WRITING A CUSTOM FIRST-STAGE DRIVER
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Condition Codes E$OK BS$E$BUFFER$SI
Page 122 and 123:
Output Parameter exception$ptr Desc
Page 124 and 125:
Condition Codes E$OK BS$E$TRANSMISS
Page 126 and 127:
END CODE; END SAMPLE_BS$RECEIVE; Co
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
WRITING A CUSTOM THIRD-STAGE DRIVER
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 158:
7.1 INTRODUCTION ERROR HANDLING 7 I
Page 161 and 162:
ERROR HANDLING 7-4 Error Code: 13 D
Page 163 and 164:
ERROR HANDLING Table 7-1. Postmorte
Page 166 and 167:
A.1 INTRODUCTION AUTOMATIC A BOOT D
Page 168 and 169:
AUTOMATIC BOOT DEVICE RECOGNITION A
Page 170 and 171:
AUTOMATIC BOOT DEVICE RECOGNITION (
Page 172 and 173:
PROMMING THE BOOTSTRAP B LOADER AND
Page 174 and 175:
C.1 OVERVIEW D-MON386 MONITOR C Int
Page 176 and 177:
%Again 3-29, 3-31 %Auto 3-15 %Auto
Page 178 and 179:
BS$SEND 5-18, 5-19 BS$SEND$RSVP 5-1
Page 180 and 181:
E Editing BSl.A86 3-8, 5-38 Error c
Page 182 and 183:
Intel-supplied first stage drivers
Page 184 and 185:
Send transition model 5-18 Serial c
Page 188 and 189:
INTEL CORPORATION 3065 Bowers Avenu
Page 190:
inter • • • • • • •
show all

using the bootstrap loader

Create successful ePaper yourself

Delete template?

Save as template?