DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1
3-21
GN
Go To Next Instruction
GN
3.11 GO TO NEXT INSTRUCTION
GN
Use the GN command to set a temporary breakpoint at the next instruction’s address, that is, the
one following the current instruction. GN then starts target code execution. After setting the
temporary breakpoint, the sequence of events is similar to that of the GO command. If there is
already a breakpoint at the tempory breakpoint location, the breakpoint must have a count less
than or equal to one or an error occurs.
GN is helpful when debugging modular code, because it allows the user to trace through a
subroutine call as if it were a single instruction.
EXAMPLE
The following section of code resides at $6000.
CPU32Bug>MD 6000:4;DI<CR>
00006000
7003
MOVE.L
#$3,D0
00006002
7201
MOVEQ.L
#$1,D1
00006004
61000FFA
BSR.W
$7000
00006008
2600
MOVE.L
D0,D3
CPU32Bug>
The following simple subroutine resides at address $7000.
CPU32Bug>MD 7000:2;DI<CR>
00007000
D081
ADD.L
D1,D0
00007002
4E75
RTS
CPU32Bug>
Execute up to the BSR instruction.
CPU32Bug>RM PC<CR>
PC =00003000 ? 6000.<CR>
CPU32Bug>GT 6004<CR>
Effective address: 00006004
Tempory breakpoint at $6004.
Effective address: 00006000
Current PC at $6000.
At Breakpoint
PC
=00006004
SR
=2700=TR:OFF_S_7
VBR
=00000000
SFC
=0=F0
DFC
=0=F0
USP
=00003830
SSP*
=00010000
D0
=00000003
D1
=00000001
D2
=00000000
D3
=00000000
D4
=00000000
D5
=00000000
D6
=00000000
D7
=00000000
A0
=00000000
A1
=00000000
A2
=00000000
A3
=00000000
A4
=00000000
A5
=00000000
A6
=00000000
A7
=00010000
00006004
61000FFA
BSR.W
$7000
CPU32Bug>
Содержание 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 ...