DEBUG MONITOR COMMANDS
M68CPU32BUG/D REV 1
3-26
GT
Go To Temporary Breakpoint
GT
3.13 GO TO TEMPORARY BREAKPOINT
GT <addr>[:<count>]
Use the GT command to set a temporary breakpoint and start target code execution. A count may
be specified with the temporary breakpoint. Control is given at the target PC address. All
previously set breakpoints are enabled. The temporary breakpoint is removed when any
breakpoint with 0 count is encountered.
After setting the temporary breakpoint, the sequence of events is similar to that of the GO
command. At this point control is returned to CPU32Bug by:
•
Executing the .RETURN SYSCALL (TRAP #15) function
•
Press the ABORT switch or RESET switch of the M68300PFB Platform Board
•
Encountering a breakpoint with 0 count
•
Generation of an unexpected exception
EXAMPLE
The following program resides at $4000.
CPU32Bug>MD 4000;DI<CR>
00004000
2200
MOVE.L
D0,D1
00004002
4282
CLR.L
D2
00004004
D401
ADD.B
D1,D2
00004006
E289
LSR.L
#$1,D1
00004008
66FA
BNE.B
$4004
0000400A
E20A
LSR.B
#$1,D2
0000400C
55C2
SCS
D2
0000400E
60FE
BRA.B
$400E
CPU32Bug>RM D0<CR>
Initialize D0 and set a breakpoint:
D0 =00000000 ? 52A9C.<CR>
CPU32Bug>BR 400E<CR>
BREAKFOINTS
0000400E
CPU32Bug>
Set PC to beginning of program, set temporary breakpoint, and start target code:
CPU32Bug>RM PC<CR>
PC =0000400E ? 4000.<CR>
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 ...