using the bootstrap loader

More documents

Recommendations

Info

WRITING A CUSTOM FIRST-STAGE DRIVER 5.5 USING THE MULTIBUS® II TRANSPORT PROTOCOL If the driver you are creating functions within a MUL TIBUS I environment, you need not read this section. Skip to Section 5.6. If the driver you are creating functions within a MUL TIBUS II environment, you must write the driver code to use the MUL TIBUS II message transport protocol. To help you accomplish this task, Intel provides a small, single-thread communication system that enables Bootstrap Loader drivers to communicate with device controllers within a MUL TIBUS II environment. This communication system is called the Bootstrap Loader Communication System. The following paragraphs provide an overview of the Bootstrap Loader Communication System, which uses concepts similar to the Nucleus Communication System. Should you desire a more complete description of these communication system concepts, refer to the iRMX® II Nucleus User's Guide. The Bootstrap Loader Communication System can be thought of as a subset of the Nucleus Communication System. It fully conforms to the MUL TIBUS II transport protocol suitable for a limited bootloading environment. Unlike the Nucleus Communication System, the Bootstrap Loader Communication system is designed to handle bootstrap loading only. As a result, the system is synchronous in nature. In other words, procedures execute to completion one after the other; no multitasking or need to handle asynchronous events exists. MUL TIBUS II transport protocol functions supported by the Bootstrap Loader Communication System include: • control and data message types, • a subset of the request/response transaction model, • send and receive transaction models, • message broadcasting, • access to device interconnect space. To support these functions, Intel supplies a set of system utilities grouped together in a Bootstrap Loader Message Passing System Module. As a programmer, you have access to these utilities through system calls you place in your driver code. The remainder of this section explains the supported functions in the Bootstrap Loader Communications System and shows you how to use each of the utilities. Bootstrap Loader 5-11
WRITING A CUSTOM FIRST-STAGE DRIVER 5.5.1 Message Types The Bootstrap Loader Communication System supports two types of messages: control messages and data messages. Control messages consist of only a control portion. These messages occur between the sender and receiver requiring no explicit buffer resource allocation. The reason for no buffer allocation is because a control message has no data part. The maximum length of a control message is 20 bytes. Also, a one-to-one correspondence exists between control messages and MUL TIBUS II unsolicited messages (all unsolicited messages are control messages). Data messages consist of both a 16-byte control portion and a variable length data portion. These messages do require explicit buffer allocation between the sender and receiver. The reason buffer allocation is required is because this type of message contains a variable amount of data. The maximum length of the data portion is 64K-l bytes. 5.5.2 Request/Response Transaction Model The Bootstrap Loader Communication System supports a subset of the request/response transaction model that the Nucleus Communication System uses. This subset has the following characteristics: • Because the Bootstrap Loader Communication System functions within a bootloading environment, request messages originate only from the host CPU board. The specific device controllers then match responses to requests on a one-to-one basis. • No support exists for multiple outstanding requests. • Fragmentation and transmission of response messages into specific application buffers can occur. Because this fragmentation is completely transparent to the user, the fragmented response is considered as a single response to a single request. • The Bootstrap Loader Communication System receives messages in the order in which they are sent. Communication between the CPU host board executing the driver and the bootable device controller uses the basic transmission model of send and receive. The driver sends a request to the device controller and then receives a response back. When the driver initiates the message, an internal transaction ID is generated that logically associates the request with the response. This ID remains valid until the device controller responds, thus completing the transaction. 5-12 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 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 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 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?