Table of Contents
Advertisement
VE
Now change the program in memory and perform the verification again.
CPU32Bug>M 4002<CR>
00004002 D088 ? D089.<CR>
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>
S30D65004000------88--------77
CPU32Bug>
The byte which was changed in memory does not compare with the corresponding byte in the S-
record.
M68CPU32BUG/D REV 1
Verify S-Records Against Memory
3-71
DEBUG MONITOR COMMANDS
Blank line as the BCC waits for an S-record.
Signal verification completion.
Record did not verify.
VE
Advertisement
Table of Contents
