~STANDARD DB~ECT CODE FORMAT
11.3 LOADING THE BNPFHL UTILITY PROGRAM Proceed as follows:
1. Load the TXDS Control Program in accordance with the step-by-step procedure pre-sented in Section II in this manual.
2. Place the TXDS diskette containing the BNPFHL utility program in an available disc' (where a number is entered for <bias>, <unit>, or <pos>
MEMORY: <beg addr>,<end addr>
" .. "
'. :',:-'~k~t 11-3 Digital Systems Division
~ 9462S8~9701
(The MEMORY: prompt is printed or displayed on the system console after the BNPFHL utility program is loaded as described in paragraph 11.3.4.)
The responses to the INPUT:, OUTPUT:, OPTIONS:, and MEMORY: prompts are described in the following subparagraphs.
NOTE
All numerical input values in response to any of the prompts are assumed to be decimal. However, another base may be specified by using the following prefixes:
PrefIX
>
Base Octal Hexadecimal
Example
!23 (equals decimal 19)
>23 (equals decimal 35)
11.3.1 RESPONSE TO THE INPUT: PROMPT. The response to the INPUT: prompt is either the pathname of a file or the pathname of a device. One of these two responses must be specified. When a DUMP or COMPARE option is specified, the file or device should contain a standard object code module. When a LOAD option is specified, the input file or device should contain either a BNPF of High-Low formatted module to correspond with the BNPF or HILO response to the OPTIONS:
prompt.
11.3.2 RESPONSE TO THE OUTPUT: PROMPT. The response to the OUTPUT: prompt is either the pathname of a file or the pathname of a device. One of these two responses must be specified.
When the COMPARE option is specified, the response to the OUTPUT: prompt should be a file which contains a BNPF or a HILO formatted module, depending upon whether a BNPF or a HILO file is to be compared to the input standard object code. The output device should not be a hard copy device or VDT because no carriage control is included in the output.
11.3.3 RESPONSE TO THE OPTIONS: PROMPT. The response to the OPTIONS: prompt is described in the following subparagraphs.
NOTE
All options must be separated by commas. The Bias, Initialization, and Position options can be defaulted as explained below, but, when used, must be specified in the following sequence: Bias, Initializa-tion, and Position.
11.3.3.1 BNPF and HILO Options. The BNPF option specifies a BNPF formatted input or out-put module and the HILO option specifies a High-Low formatted inout-put or outout-put module. Either the BNPF or HILO option must be specified. The abbreviations BN and HI may be used, respec-tively, instead of the full four characters. When neither the BNPF option or the High-Low option is specified, an error results.
11.3.3.2 DUMP, COMPARE, and LOAD Options. The use of these options is described in the following subparagraphs.
NOTE
1. One of these options must be specified or an error will result.
2. Each of the option names may be abbreviated by using the first two letters in the option name
11-4 Digital Systems Division
~
____ 9_4_6_2_58_-9_7_0_1 ________________________ _DUMP (DU) Option. The DUMP option causes the input file in 990 standard object code to be dumped to the output file in the specified BNPF or High-Low format.
COMPARE (CO) Option. The COMPARE option is used to verify the results of a DUMP by comparing the output BNPF or HILO formatted file to the input file in standard object code format.
When there is no discrepancy in a BNPF COMPARE, the beginning and end addre~s of the com-pared information or data are printed on the system console. The following printout is an example of a BNPF COMPARE without errors:
TXBNPF V.R.E YY.DDD
PROGRAM: :BNPFHL/SYS INPUT: DSC2 :LIGHTS/OBJ OUTPUT: DSC2:TEMP/OBJ OPTIONS: BN, CO
TXBNPF_ V .R.E.-~YY:DDD TXBNPF HI/LO UTILITY MEMORY: 0, 24
BEG ADDR=OOOO END ADDR=0018
TXDS V.R.E YY.DDD
PROGRAM:
When there is no discrepancy in a HILO COMPARE, no printout or display is presented on the system console.
When a BNPF COMPARE is discrepant, a presentation of the discrepancy is printed out or displayed on the system console. An example of a typical printout or display of a discrepancy is:
T0064=9C M0064=38 where:
T represents the BNPF output file; 0064 represents the decimal address of the byte; and 9C represents the hexadecimal value of the byte, and
where:
M represents the input file in standard object code; 0064 represents the decimal address of the byte; and 38 represents the hexadecimal value of the byte.
The discrepancy is noted by the difference in hexadecimal byte-values 9C and 38. When there exists no discrepancy, both hexadecimal byte-values are 38 and, as a result, are not printed out or displayed on the system console.
When a HILO COMPARE is discrepant, a presentation of the discrepancy is printed out or displayed on the system console. An example of a typical printout or display of a discrepancy is:
M0003.<0,3>=0000 T0003.<0,3>=2000
11-5 Digital Systems Division
~
946258-9701 where:M represents the input file in standard object code; 003 represents the decimal address of the ( input file word; 0,3 represents the beginning and ending bit positions of the four-bit string in the input object file; and 0000 represents the hexadecimal value of the input file word; and where:
T represents the HILa output file; 0003 represents the decimal address of the output file word; 0,3 represents the beginning and ending bit positions of the discrepant four-bit string in the output file; and 2000 represents the hexadecimal value of the output file word.
The discrepant output is presented in hexadecimal word format but, nevertheless, represents the High-Low formatted output from the HILa DUMP program execution. In addition, the discrepancy is noted by the difference in hexadecimal word-values 0000 and 2000. When there exists no dis-crepancy, both hexadecimal word-values are 0000 and, as a result, are not printed out or displayed on the system console.
LOAD (La) Option. Selection of the LOAD option causes a previously created BNPF or High-Low formatted file to be~<:)!!verted into an output file_ which can be used to prograJl!
PROMs using the PROM Programming Module (i.e. the hardware module). Refer to the TXDS (TXPROM) Programmer Utility Program section in the TXDS Programmer.s-Guide, manual number 946258-9701.
11.3.3.3 Bias (B<bias» Option. The Bias option supplements the DUMP and COMPARE options.
It defines the number to be added to the address of the relocatable data in the input file as well as to the relocatable data itself for the purpose of producing the output file or for the purpose of com-paring the input file to the output file. The BIAS option has no effect on nonrelocatable object module data. The default-substitute produced by the utility program is O. An example of the use of the Bias option is presented in paragraph 11.5.5. The bias must immediately follow the B.
11.3.3.4 Initialization (I<init» Option. The Initialization option is used to initialize the buffer area into which the input file's standard object code is to be read. This initialization is done prior to converting the input file to the BNPF or HILa format so that each bit position initially contains a 1 or O. Unused sections of the buffer are also initialized. The default substitute provided by the utility program for the Initialization option is O. The operator must enter a 0 or I immediately after the I. Whenever a number other than 0 or 1 is specified an error results. An example of the use of the Initialization option is presented in paragraphs 11.5.3 and 11.5.4.
11.3.3.5 Position (P<pos» Option. The Position option specifies the first bit of the four-bit string from each of the input-file-words (which are in the format of standard object code) that are to be ' converted to the HILa format. A Position option number from 0 through 12 is selected by the operator to supplement the HILa option selection. The selected number specifies the position number of the start-bit of the four-bit string of the 16-bit word from the input file's standard object code. An example of the use of the Position option is presented in paragraph 11.5.3. The bit position parameter must immediately follow the P.
11-6 Digital Systems Division
c
(
~r15\
~_ _ _ _ _ _
946258-9701_
11.3.4 RESPONSE TO THE MEMORY: PROMPT. The operator's response to the MEMORY:
prompt is used to specify the bounds for a BNPF or HILO format. These bounds must be word ad-4resses (even) for HILO format, but may be byte addresses for BNPF format. The first boundary is the address of the first word or byte to be formatted. The second boundary is the address oftne last word or byte to be formatted. The boundaries must be separated by a comma. When the addresses are hexadecimal, they must be preceded by a ">" character. It is not necessary to fonnat a whole object module.
Following is an example of a BNPF format MEMORY: prompt. The module was assembled using an AORG >AO directive which causes the assembler to generate absolute addresses starting at >AO.
The module is >6C bytes long.
MEMORY: >AO, >lOB
>AO is the address of the first byte to be formatted and> 1 OB is the address of the last byte to be formatted.
Following is an example of a HILO format MEMORY: prompt. The module was assembled as a relocatable module. The module is >SE bytes long.
MEMORY: 0, >SC
The address of the first word is zero, the address of the last word is >SC.
NOTE
The starting and ending address may be obtained from an assembly listing that is generated with the object module.
In the event the end address entered in response to the MEMORY: prompt exceeds the capacity of memory, the CANNOT GET MEMORY error message is printed or displayed on the system console.
11-7 Digital Systems Division
~
~ . . o _ _ _ _ _ _ 946258-9701 _NOTE
1. The HILO option produces an error message when a byte boundary is specified.
2. The MEMORY: prompt is -not issued when the LOAD option is used.
11.4 ERROR MESSAGES
The error messages that result from misuse of the BNPFHL utility are listed in table 11-1 with an explanation of the cause of each error.