Motorola M68CPU32BUG User Manual page 47

Debug monitor
Table of Contents

Advertisement

DU
Dump 10 bytes of memory beginning at $3000 to terminal screen (port 0).
CPU32Bug>DU 3000:&10;B<CR>
Effective address: 00003000
Effective count
: &10
S0003000FC
S10D3000000000040008000C00109A
S9030000FC
CPU32Bug>
Dump memory from $4000 to $402F to host (port 1). Specify a file name of ''TEST'' in the S0
header record and specify an entry point of $400A.
CPU32Bug>DU 1 4000 402F 'TEST' 400A<CR>
Effective address: 00004000
Effective address: 0000402F
CPU32Bug>
The following example illustrates the procedure for uploading S-records to a host computer, in
this case an IBM-PC or compatible running MS-DOS with the ProComm terminal emulation
utility. Assume memory from $4000 to $4007 is initialized as follows:
CPU32Bug>MD 4000:4;DI<CR>
00004000
7001
00004002
D089
00004004
4A00
00004006
4E75
CPU32Bug>
Enter the following command to dump S-records from memory locations $4000-$4007 with a
start address of $4000, a title of 'TEST.MX', and an offset of $65000000. Before entering the
<CR> to send the DU command to CPU32Bug, enter the ProComm command <ALT-F1> keys
to open a log file. Enter the filename as TEST.MX. Then enter the carriage return, <CR> to
complete the DU command entry. The DU command output is sent to the screen and ProComm
copies it into the file TEST.MX.
CPU32Bug>DU 4000 4007 'TEST.MX' 4000 65000000<ALT-F1><CR>
Effective address: 00004000
Effective address: 00004007
S00A0000544553542E4D58E2
S30D650040007001D089A004E7576
S7056500400055
CPU32Bug>
M68CPU32BUG/D REV 1
Dump S-Records
MOVEQ.L
ADD.L
TST.B
RTS
3-17
DEBUG MONITOR COMMANDS
#$1,D0
A1,D0
D0
DU

Advertisement

Table of Contents
loading

Table of Contents