Motorola M68CPU32BUG Manuel d'utilisateur télécharger pdf (Page 68)

APPENDIX A

M68332BCC/D A-4 MOTOROLA

REV 1

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 INSTRUCTION

285F MOVE.L (A7)+,A4

245F MOVE.L (A7)+,A2

2212 MOVE.L (A2),D1

226A0004 MOVE.L 4(A2),A1

24290008 MOVE.L FUNCTION(A1),D2

237C MOVE.L #FORCEFUNC,FUNCTION(A1)

(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 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:

0101 0011 0011 0001 0011 0001

TYPE

0011 0011 0011 0000 0011 0000 0011 0000 0011 0000 0011 0010 0011 1000 0011 0101 0100 0110 ••• 0011 0010 0100 0001

533131 33030303032383546•••3241

S1130000285F•••2A

LENGTH ADDRESS CODE/DATA CHECKSUM

1 2 ... 63 64 65 66 67 68

Pas de commentaire

Motorola M68CPU32BUG Manuel d'utilisateur Page 68