Table of Contents
Advertisement
S-RECORD INFORMATION
Each record may be terminated with a CR/LF/NULL. Additionally, an S-record may have an
initial field to accommodate other data such as line numbers generated by some time-sharing
systems.
Accuracy of transmission is ensured by the record length (byte count) and checksum fields.
A-3 S-RECORD TYPES
Eight types of S-records have been defined to accommodate the several needs of the encoding,
transportation, and decoding functions. The various Motorola upload, download, and other
record transportation control programs, as well as cross assemblers, linkers, and other file-
creating or debugging programs, utilize only those S-records which serve the purpose of the
program. For specific information on which S-records are supported by a particular program, the
user manual for that program must be consulted.
The EVBU monitor supports only the S1 and S9 records. All data
before the first S1 record is ignored. Thereafter, all records must be
S1 type until the S9 record terminates data transfer.
An S-record format module may contain S-records of the following types:
S0
The header record for each block of S-records. The code/data field may contain any descriptive
information identifying the following block of S-records. The address field is normally zeroes.
S1
A record containing code/data and the 2-byte address at which the code/data is to reside.
S2-S8
Not applicable to EVBU.
S9
A termination record for a block of S1 records. The address field may optionally contain the 2-
byte address of the instruction to which control is to be passed. If not specified, the first entry
point specification encountered in the object module input will be used. There is no code/data
field.
Only one termination record is used for each block of S-records. Normally, only one header
record is used, although it is possible for multiple header records to occur.
A-2
NOTE
M68HC11EVBU/D
Advertisement
Table of Contents
