Using 162Bug Target Vector Table - Motorola MVME162LX 300 Series Installation And Use Manual

Using The 162Bug Debugger
4

Using 162Bug Target Vector Table

4-12
Example: Trace one instruction using debugger.
RD
162Bug>
PC =00010000 SR
USP =0000DFFC MSP
DFC =0=F0 CACR =0=........
D0 =00000000 D1
D4 =00000000 D5
A0 =00000000 A1
A4 =00000000 A5
00010000 203C0000 0001
T
162Bug>
PC =00010006 SR
USP =0000DFFC MSP
DFC =0=F0 CACR =0=........
D0 =00000001 D1
D4 =00000000 D5
A0 =00000000 A1
A4 =00000000 A5
00010006 D280
162Bug>
Notice that the value of the target stack pointer register (A7) has not
changed even though a trace exception has taken place. Your program may
either use the exception vector table provided by the 162Bug or it may
create a separate exception vector table of its own. The two following
sections detail these two methods.
The 162Bug initializes and maintains a vector table area for target
programs. A target program is any program started by the bug, either
manually with GO or TR type commands or automatically with the BO
command. The start address of this target vector table area is the base
address of the debugger memory. This address is loaded into the target-
state VBR at power up and cold-start reset and can be observed by using
the RD command to display the target-state registers immediately after
power up.
=2700=TR:OFF_S._7_.....
=0000EFFC ISP* =0000FFFC SFC
=00000000 D2 =00000000 D3
=00000000 D6 =00000000 D7
=00000000 A2 =00000000 A3
=00000000 A6 =00000000 A7
MOVE.L #$1,D0
=2700=TR:OFF_S._7_.....
=0000EFFC ISP* =0000FFFC SFC
=00000000 D2 =00000000 D3
=00000000 D6 =00000000 D7
=00000000 A2 =00000000 A3
=00000000 A6 =00000000 A7
ADD.L D0,D1
Computer Group Literature Center Web Site
VBR =00000000
=0=F0
=00000000
=00000000
=00000000
=0000FFFC
VBR =00000000
=0=F0
=00000000
=00000000
=00000000
=0000FFFC