using the bootstrap loader

More documents

Recommendations

Info

USING THE BOOTSTRAP LOADER Example: Assume that an iRMX I application system is in the file /BOOT86/MYSYS on drive :WFO:. You can boot this system by entering the following command at the iSDM monitor prompt: .b :wfO:/boot86/mysys For an example using the D-MON386 monitor, refer to Appendix C. 2.2.2 Debug Option If the iSDM monitor is present in the system, you can include a debug option when specifying a load file. This option instructs the Bootstrap Loader to do the following immediately after loading is complete: • Set the CPU registers as described in Appendix A so the iRMX Operating System can detect that the debug option was set. iRMX will then execute an interrupt 3 instruction to enter the monitor. Set a breakpoint at the first instruction to be executed by the application system. For iRMX I systems, the breakpoint will be set in the load file. For iRMX II systems, the load file (the third stage) will be loaded as always and it will load the application system. The breakpoint will then be set in the application system. • Pass control to the iSDM monitor, which displays an "Interrupt 3 at " message at the terminal, displays its prompt and waits for a command from the terminal. (The monitor prompt is a single period for real-mode iRMX I systems or two periods for protected-mode iRMX II systems.) At this poinfyou can invoke any of the iSDM monitor commands that are appropriate for real or protected mode. (To continue running the loaded program, enter G < cr > .) One advantage of the Debug switch is that the monitor's interrupt message tells you that the loading process was successful. If a system you are booting fails, you might not otherwise be able to tell whether the bootstrap load itself was unsuccessful, or whether the system loaded successfully and then failed during initialization. The presence or absence of the interrupt message when you use the Debug option clarifies whether the loading was successful. Because the Debug option leaves you in the monitor, you can alter the contents of specific memory locations and do other monitor actions (such as debugging) before you start your system running with the monitor's G command. To use the Debug option when you are invoking the Bootstrap Loader from the iSDM monitor, include the letter D in the command line immediately after the B (boot) command. Specify any load file pathname after the Band D characters. Bootstrap Loader 2-3
USING THE BOOTSTRAP LOADER 2-4 For example, any of the following command lines invoke the Bootstrap Loader (from the iSDM monitor) with the Debug option: .bd .b d .bd /boot86/28612 .b d :wO:boot86/28612 Notice that the "D" and any pathname must be separated by at least one space. You can also use the Debug option on systems in which the Bootstrap Loader is configured to request the load file name. These systems display the Bootstrap Loader's first stage asterisk (*) prompt. Place the "D" and at least one space in the command line before the load file specification. Examples of this are: *d * d *d /boot86/28612 * d :wO:boot86/28612 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: USING THE BOOTSTRAP LOADER 2-2 When
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?