using the bootstrap loader

More documents

Recommendations

Info

2.4 CHOOSING A THIRD STAGE USING THE BOOTSTRAP LOADER If you plan to load iRMX II applications, you must include a version of the Bootstrap Loader's third stage on the secondary storage device from which you are loading your application. You can use the following types of third stages, depending on the type of system you are loading. • A generic third stage • A default device-specific third stage • A remote third stage • Your own configuration of the device-specific third stage containing customized device drivers. The rest of this section should help you decide which third stage best suits your needs. The important elements to consider when you choose a third stage are the size of your system, the type of mass storage devices used to boot your system, and the CPU board you are using. If you plan to load your system from any of the Intel-supplied devices, you can use: 1. the default device-specific third stage regardless of the size of your system, or 2. a default generic or remote third stage for systems up to 840K bytes. All third stages are supplied for 80286 and 386 N CPU boards. If you plan to load your system from a custom device, the size of the system determines which third stage you should use. • For systems that are not expected to exceed 840K bytes, use the generic third stage. In this case, you do not need to supply a custom device driver for the third stage. You will already be supplying a custom first stage driver; the generic third stage will use that same driver to access the custom device. • If your application exceeds 840K bytes, you must use the device-specific third stage, because it switches the processor into protected mode before loading the application. This enables the third stage to load into the entire 16 megabyte address space supported by protected mode. However, to load applications from your custom device, you must write a third stage device driver for your device. This driver can be a modification of your first stage driver that runs in the processor's protected mode. For information on writing a third stage driver, refer to Chapter 6. • If your application will be loaded from a remote device, you must use the remote third stage. Bootstrap Loader 2-7
USING THE BOOTSTRAP LOADER * 2-8 NOTE The 840K byte limit on systems loaded by the generic and remote third stages applies to the boot file only. Once the boot file is loaded and has control, the entire 16 megabytes of memory address space is available for the system (both the free space manager and the Application Loader). Table 2-1 lists the versions of the third stage that are supplied on the Bootstrap Loader Release Diskettes. This table enables you to pick the appropriate third stage for your system. After you install your system, these files are available in the /BSL directory. Table 2-1. Supplied Third Stage Files Device-Specific Generic Remote CPU Board Third Stage Third Stage Third Stage iSBC 286/10 28612 28612.GEN 28612.REM iSBC 286/10A 28612 28612.GEN 28612.REM iSBC 286/12 28612 28612.GEN 28612.REM iSBC386/12 38612 38612.GEN 38612.REM iSBC 286/100A 286100A 2861ooA.GEN iSBC386/2X 38620 38620.GEN 38620. REM iSBC386/3X 38620 38620.GEN 38620. REM iSBC 386/116* 386100 3861oo.GEN iSBC 386/120* 386100 3861oo.GEN This usage of any third stage with these CPU boards is possible only if they do not use the MSA 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 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: USING THE BOOTSTRAP LOADER 2-6 Alth
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?