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

ASSEMBLER/DISASSEMBLER

M68CPU32BUG/D 4-2

4.1.2 M68300 Family Resident Structured Assembler Comparison

There are several major differences between the CPU32Bug assembler and the M68300 Family

resident structured assembler. The resident assembler is a two-pass assembler that processes an

entire program as a unit, while the CPU32Bug assembler processes each line of a program as an

individual unit. Due mainly to this basic functional difference, the CPU32Bug assembler

capabilities are more restricted:

• Label and line numbers are not used. Labels are used to reference other lines and

locations in a program. The one-line assembler has no knowledge of other lines and,

therefore, cannot make the required association between a label and the label

definition located on a separate line.

• Source lines are not saved. In order to read back a program after it is entered, the

machine code is disassembled and then displayed as mnemonics and operands.

• Only two directives (DC.W and SYSCALL) are accepted.

• No macro operation capability is included.

• No conditional assembly is used.

• No structured assembly is used.

• Several symbols recognized by the resident assembler are not included in the

CPU32Bug assembler character set. These symbols include ’’>’’ and ’’<’’. Three other

symbols have multiple meaning to the resident assembler, depending on the context.

These are:

Asterisk (*)-Multiply or current PC

Slash (/)-Divide or delimiter in a register list

Ampersand (&)-And or decimal number prefix

Although functional differences exist between the two assemblers, the one-line assembler is a

true subset of the resident assembler. The CPU32Bug assembler format and syntax are acceptable

to the resident assembler except as described above.

4.2SOURCE PROGRAM CODING

A source program is a sequence of source statements arranged in a logical manner to perform

predetermined tasks. Each source statement occupies a line and must be either an executable

instruction, a DC.W directive, or a SYSCALL assembler directive. Each source statement

follows a consistent source line format.

DEBUG MONITOR COMMANDS

M68CPU32BUG/D REV 1 3-71

VE Verify S-Records Against Memory VE

Now change the program in memory and perform the verification again.

CPU32Bug>M 4002<CR>

00004002 D088 ? D089.<CR>

CPU32Bug>VE -65000000<CR>

Blank line as the BCC waits for an S-record.

Enter the terminal emulator’s escape key to return to the host computer’s operating system (ALT-

F4 for ProComm). A host command is then entered to send the S-record file to the port where the

BCC is connected (for MS-DOS based host computer this would be "type test.mx >com1", where

the BCC was connected to the com1 port).

After the file has been sent, the user then restarts the terminal emulation program (for MS-DOS

based host computers, enter EXIT at the prompt).

Since the port number equals the current terminal, two <CR>’s are required to signal CPU32Bug

that verification is complete and the terminal emulation program is ready to receive the status

message.

Signal verification completion.

S30D65004000------88--------77

Record did not verify.

CPU32Bug>

The byte which was changed in memory does not compare with the corresponding byte in the S-

record.

eescale S

emiconduct

, I

Freescale Semiconductor, Inc.

For More Information On This Product,

Go to: www.freescale.com

nc...

1 2 ... 46 47 48 49 50 51 52 53 54 55 56 ... 97 98

Commentaires sur ces manuels

Pas de commentaire

Motorola M68CPU32BUG Manuel d'utilisateur Page 51

Commentaires sur ces manuels

Produits connexes et manuels pour Téléviseurs et moniteurs Motorola M68CPU32BUG