USER CUSTOMIZATION
M68CPU32BUG REV 1
C-3
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.
<CR><CR>
Verify passes.
CPU32Bug>
7. Verify the main S-record file, C32B23.MX, by entering the command shown below.
No offset is required.
CPU32Bug>VE<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 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.
<CR><CR>
Verify passes.
CPU32Bug>
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
Страница 16: ...GENERAL INFORMATION M68CPU32BUG D REV 1 1 8 ...
Страница 30: ...DEBUG MONITOR DESCRIPTION M68CPU32BUG D REV 1 2 14 ...
Страница 102: ...DEBUG MONITOR COMMANDS M68CPU32BUG D REV 1 3 72 ...
Страница 168: ...DIAGNOSTIC FIRMWARE GUIDE M68CPU32BUG D REV 1 6 24 ...