Motorola M68CPU32BUG User Manual page 177

Debug monitor
Table of Contents

Advertisement

6.
Verify the customized S-record file, C32B1.MX, by entering the command shown
below. The -DC000 offset is required to relocate the verification from the $E0000
base address of the S-records to the RAM change area at $4000.
CPU32Bug>VE -DC000<CR>
Enter the terminal emulator's escape key to return to the host computer's operating
system (ALT-F4 for ProComm). Then enter the host command to send the S-record
file to the port where the BCC is connected (type c32b.mx >com1, when the BCC is
connected to the com1 port).
After the file has been sent, restart the terminal emulation program by entering EXIT
on the host computer. Then enter two <CR>'s to signal the CPU32Bug that
verification is complete and the terminal emulator program is ready to receive the
status message.
7.
Verify the main S-record file, C32B23.MX, by entering the command shown below.
No offset is required.
Enter the terminal emulator's escape key to return to the host computer's operating
system (ALT-F4 for ProComm). Then enter the host computer command to send the
S-record file to the BCC (type c32b23.mx >com1, when the BCC is connected to the
com1 port).
After the file has been sent, restart the terminal emulation by entering EXIT on the
host computer. Then enter two <CR>'s to signal the CPU32Bug that verification is
complete and the terminal emulator program is ready to receive the status message.
8.
Follow the PROGBCC utility (available on FREEWARE) directions for
reprogramming the BCC EPROM using the two S-record files, C32B1.MX and
C32B23.MX.
M68CPU32BUG REV 1
<CR><CR>
Verify passes.
CPU32Bug>
CPU32Bug>VE<CR>
<CR><CR>
Verify passes.
CPU32Bug>
C-3
USER CUSTOMIZATION

Advertisement

Table of Contents
loading

Table of Contents