Table of Contents
Advertisement
LO
EXAMPLES
Suppose a host computer was used to create a program that looks like this:
1
2
3
65004000
4
5
65004000
7001
6
65004002
D088
7
65004004
4A00
8
65004006
4E75
9
END
****** TOTAL ERRORS
****** TOTAL WARNINGS
Then this program was converted into an S-record file named TEST.MX as follows:
S00F00005445535453335337202001015E
S30D650040007001D0884A004E7577
S7056500400055
Load this file into BCC memory for execution at address $4000 as follows:
CPU32Bug>LO -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 the download is complete and the terminal emulation program is ready to receive any error
messages.
<CR><CR>
CPU32Bug>
M68CPU32BUG/D REV 1
Load S-Records From Host
*
Test Program.
*
ORG
MOVEQ.L
ADD.L
TST.B
RTS
0--
0--
3-33
DEBUG MONITOR COMMANDS
$65004000
#1,D0
A0,D0
D0
Blank line as the BCC waits for an S-record.
Signal download completion.
No error messages.
LO
Advertisement
Table of Contents
