using the bootstrap loader

More documents

Recommendations

Info

5.1 INTRODUCTION 5 WRITING A CUSTOM FIRST-STAGE DRIVER You can configure the Bootstrap Loader to run with many kinds of devices. If you plan to use one of the devices for which Intel supplies a device driver, you can skip this chapter. If you plan to write a driver for the MULTIBUS@II System Architecture (MSA) Bootstrap Loader, refer to the MULTIBUS@ II System Architecture (MSA) Bootstrap Loader Specification rather than this manual. If you want to use the Bootstrap Loader with a device other than those supported by Intel, you must write your own first-stage device driver. (If you want to load iRMX II applications past the first megabyte of address space, you must also write a custom thirdstage driver. Chapter 6 describes how to write third-stage drivers.) This chapter provides you with guidelines for writing a custom first-stage driver. You must include two procedures in every first-stage device driver: a device initialize procedure and a device read procedure. The device initialize procedure must initialize the bootstrap device. The device read procedure must load information from the device into RAM. The rest of this chapter refers to the two procedures as DEVICE$INIT and DEVICE$READ. However, you can give them any names you want, provided no other first-stage driver procedure uses the chosen names. To check the names of the Intelsupplied first-stage procedures, use LIB86 to list the modules in the object library /BSL/BS l.LIB. You must write both procedures in an 8086 language (either PL/M-86 or ASM86) and conform to the LARGE model of segmentation of the PL/M-86 programming language. This means that you must declare the two procedures as FAR (not NEAR) and all pointers must be 32 bits long. You must adhere to the interfacing and referencing conventions of the PL/M-86 LARGE model even if you write the procedures in assembly language. Bootstrap Loader 5-1
WRITING A CUSTOM FIRST-STAGE DRIVER 5-2 If your driver code is going to operate in a MUL TIBUS II environment which does not use the MUL TIBUS II System Architecture bootstrap protocol, two additional driver code constraints exist. First, you must follow the MUL TIBUS II transport protocol for communication between the driver and the device controller you bootstrap load from. You can accomplish this by using Bootstrap Loader Communication System utility calls within your driver code. Second, you must organize your driver code so that it belongs to the BSL-Drivers COMPACT sub-system. This last requirement is necessary because the Bootstrap Loader Communication System utilities are all NEAR calls. The next two sections describe the interface these two procedures must present to the firststage Bootstrap Loader code. Later sections describe how to supply configuration information to the driver, how to use Bootstrap Loader Communication System utilities in your driver code, and how to generate first-stage Bootstrap Loader code that includes the new 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 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 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 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 136: WRITING A CUSTOM FIRST-STAGE DRIVER
Page 145 and 146: WRITING A CUSTOM THIRD-STAGE DRIVER
Page 155 and 156:
WRITING A CUSTOM THIRD-STAGE DRIVER
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?