using the bootstrap loader

More documents

Recommendations

Info

OVERVIEW OF BOOTSTRAP LOADER OPERATIONS The following are examples of valid and invalid third stage/load file combinations: Valid Combinations Third stage- Load file-- Third stage - Load file-- Invalid Combinations Third stage - Load file-- Third stage - Load file-- MYSYS MYSYS.286 SYS1.3RD SYS1.286 MYSYS YOURSYS.286 MYSYS.3RD MYSYS.LOD When you configure the first stage of the Bootstrap Loader, you can choose the file name that will be used if the operator doesn't specify a filename when invoking the Bootstrap Loader. By default, the file name is /SYSTEM/RMX86 for iRMX I load files. For iRMX II systems, /SYSTEM/RMX86 is the default name of the Bootstrap Loader's third stage and /SYSTEM/RMX86.286 is the default name of the iRMX II load file. This name was chosen for iRMX II systems to enable it to use the defaults in the Intel microcomputer system firmware. NOTE Because of the way the Bootstrap Loader interprets filenames, the only period (.) allowed in the entire pathname for the load file is the one that precedes the extension 286. For example, the pathname /SYSTEM.l/MYSYS.286 is invalid because it contains more than one period. If your loadfile is located on a remote system, you do not specify the actual name of the load file. Instead, you must specify a word value called the class code. The remote system must create a class code file which contains the mapping of class code values to sets of files to be loaded. In addition, the files to be loaded from a remote system must be processed with utilities provided with the iRMX-NET software product before they can be loaded. Refer to the iRMX®-NET Software Installation and Configuration Guide for a description of preparing an application system to be remote booted. Bootstrap Loader 1-7
OVERVIEW OF BOOTSTRAP LOADER OPERATIONS 1.3 DEVICE DRIVERS 1-8 When the Bootstrap Loader starts running, there is no software in place to enable the processor to communicate with the device from which you want to load the system. Part of the task of the Bootstrap Loader is to establish communications with the boot device. To communicate with devices, the Bootstrap Loader must include "programs", called device drivers, for the devices from which you want to boot. When configuring the Bootstrap Loader, you specify the device drivers you want to include. The configuration process links the drivers to the Bootstrap Loader code. Both the first stage and the device-specific third stage require their own drivers. The firststage drivers operate in real address mode and are used to load iRMX I applications and the third stage of the Bootstrap Loader. The generic third stage also uses the first-stage drivers to load iRMX II applications. The third-stage drivers operate in protected virtual address mode and are used by the device-specific third stage to load iRMX II applications into the full 16 megabyte address space. The first stage must include a real mode device driver for each device from which you want to boot. The generic and remote third stage include no drivers of their own, but the devicespecific third stage must include a protected mode driver for each of the boot devices. Intel includes several real and protected mode drivers in the Bootstrap Loader package, as listed in Table 1-1. All the real mode drivers can be used with the first stage and with the generic third stage. All the protected mode drivers can be used with the device-specific third stage. If you want to boot from a device not supported by these device drivers, you can write your own device driver. See Chapter 5 for information on writing a new device driver. 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 14 and 15: 1.1 INTRODUCTION OVERVIEW OF BOOTST
Page 16 and 17: 1.2 THE STAGES OF THE BOOTSTRAP LOA
Page 18 and 19: Generic Third Stage OVERVIEW OF BOO
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?