Freescale Semiconductor M68CPU32BUG/D CPU32Bug Debug Monitor User’s Manual

Freescale Semiconductor, Inc.
S-RECORD INFORMATION
Each record may be terminated with a CR/LF/NULL. Additionally, an S-record may have an
S-RECORDS
CREATION
initial field to accommodate other data such as line numbers A.4
generated
by some time-sharing
systems. An S-record file is a normal ASCII text file in the operating system in which it resides.
S-record format files may be produced by du
assemblers
or cross linkers.
Accuracy of transmission is ensured by the record length (byte count)
and checksum
fields. Several programs a
format from a host system to a microprocessor-ba
Freescale Semiconductor, Inc...
A.3 S-RECORD TYPES
EXAMPLE
Eight types of S-records have been defined to accommodate the several needs of the encoding,
Shown below is a typical S-record format module
transportation and decoding functions. The various Motorola upload, download and other records
transportation control programs, as well as cross assemblers, linkers S00600004844521B
and other file-creating or
S1130000285F245F2212226A0004242900
debugging programs, utilize only those S-records which serve the purpose
of the program. For
S113001000020008000826290018538123
specific information on which S-records are supported by a particular program,
the user’s manual
S113002041E900084E4223430018234200
for the program must be consulted. CPU32Bug supports S0, S1, S2, S3,S113003000144ED492
S7, S8, and S9 records.
S9030000FC
An S-record format module may contain S-records of the following types:
S0
The module
consists
one S0 record,
The header record for each block of S-records, The code/data.field
may contain
anyofdescriptive
information identifying the following block of S-records. The address field is normally zeros.
S1
A record containing code/data and the 2-byte address at which the code/data is to reside.
S2
S-record istype
S0, indicating
A record containing code/data and the 3-byte address at whichS0
the code/data
to reside.
S3
A record containing code/data and the 4-byte address at which06
the code/data
is to reside.
Hexadecimal
06 (decimal
S5
A record containing the number of S1, S2, and S3 records transmitted
in a particular block.
This
00 Four-character,
2-byte,
address
count appears in the address field. There is no code/data field.
four S1 re
The S0 record is comprised of the following char
that it is a he
6), indicating th
field; zero
00
S7
A termination record for a block of S3 records, The address field may optionally contain the 448is no code/data field.
byte address of the instruction to which control is passed. There
S8
A termination record for a block of S2 records. The address field
52may optionally contain the 3byte address of the instruction to which control is passed. There is no code/data field.
S9
A termination record for a block of S1 records. The address field may optionally contain the 2byte address of the instruction to which control is passed. If not specified, the first entry point
specification encountered in the object module input will be used. There is no code/data field.
44
1B
ASCII H, D and R - "HDR".
The checksum.
The first S1 record is explained as follows:
Only one termination record is used for each block of S-records. S7 and S8 records are usually
S1 S-record type S1, indicating that it is a co
used only when control is to be passed to a 3 or 4 byte address. Normally, only one header record
address.
is used, although it is possible for multiple header records to occur.
13 Hexadecimal 13 (decimal 19), indicating
of binary data, follow.
00
00
M68CPU32BUG REV 1
A-2
Four-character, 2-byte, address field; hexa
follows is to be loaded.
M68CPU32BUG REV 1
For More Information On This Product,
Go to: www.freescale.com
A-
">