Table of Contents
Advertisement
The next 16 character pairs of the first S1 record are the ASCII bytes of the actual program
code/data. In this assembly language example, the hexadecimal opcodes of the program are
written in sequence in the code/data fields of the S1 records:
OPCODE
285F
245F
2212
226A0004
24290008
237C
(The balance of this code is continued in the code/data fields of the remaining S1
records and stored in memory.)
2A
The checksum of the first S1 record.
The second and third S1 records also each contain $13 (19) character pairs and are ended with
checksums 13 and 52 respectively. The fourth S1 record contains 07 character pairs and has a
checksum of 92.
The S9 record is explained as follows:
S9
S-record type S9, indicating that it is a termination record.
03
Hexadecimal 03, indicating that three character pairs (3 bytes) follow.
00
00
The address field, zeros.
FC The checksum of the S9 record.
Each printable character in an S-record is encoded in a hexadecimal (ASCII in this example)
representation of the binary bits which are actually transmitted. For example, the first S1 record
above is sent as:
TYPE
LENGTH
S
1
1
5
3
3
1
3
1
3
0101 0011 0011 0001 0011 0001
0011 0011 0011 0000 0011 0000 0011 0000 0011 0000 0011 0010 0011 1000 0011 0101 0100 0110 ••• 0011 0010 0100 0001
M68CPU32BUG REV 1
INSTRUCTION
MOVE.L
MOVE.L
MOVE.L
MOVE.L
MOVE.L
MOVE.L
ADDRESS
3
0
0
0
3
3
0
3
0
3
0
(A7)+,A4
(A7)+,A2
(A2),D1
4(A2),A1
FUNCTION(A1),D2
#FORCEFUNC,FUNCTION(A1)
CODE/DATA
0
2
8
3
0
3
2
3
8
3
A-4
S-RECORD INFORMATION
CHECKSUM
5
F
•••
2
5
4
6
•••
3
2
4
A
1
Advertisement
Table of Contents
