Table of Contents
Advertisement
VE
Then converted into an S-Record file named TEST.MX as follows:
S00A0000544553542E4D58E2
S30D650040007001D0884A004E7577
S7056500400055
This file was downloaded into memory using "LO -65000000" at address $4000. The program
may be examined in memory using the MD (memory display) command.
CPU32Bug>MD 4000:4;DI<CR>
00004000 7001
00004002 D088
00004004 4A00
00004006 4E75
CPU32Bug>
To ensure the program has not been destroyed in memory, use the VE command to perform a
verification.
CPU32Bug>VE -65000000<CR>
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.
<CR><CR>
Verify passes.
CPU32Bug>
The verification passes. The program stored in memory was the same as that in the downloaded
S-record file.
M68CPU32BUG/D REV 1
Verify S-Records Against Memory
MOVEQ.L
#$1,D0
ADD.L
A0,D0
TST.B
D0
RTS
3-70
DEBUG MONITOR COMMANDS
Blank line as the BCC waits for an S-record.
Signal verfication complete.
VE
Advertisement
Table of Contents
