Hardware Functions; Exception Vectors Used By 162Bug; Table 4-2. Exception Vectors Used By 162Bug - Motorola MVME162LX 300 Series Installation And Use Manual

Hardware Functions

The only hardware resources used by the debugger are the EIA-232-D
ports, which are initialized to interface to the debug terminal. If these ports
are reprogrammed, the terminal characteristics must be modified to suit, or
the ports should be restored to the debugger-set characteristics prior to
reinvoking the debugger.

Exception Vectors Used by 162Bug

The exception vectors used by the debugger are listed below. These
vectors must reside at the specified offsets in the target program's vector
table for the associated debugger facilities (breakpoints & trace mode) to
operate.
Vector
Offset
$10
$24
$80-$B8
$BC
NOTE 1
NOTE 2
$DC
NOTES:
When the debugger handles one of the exceptions shown in Table 4-2, the
target stack pointer is left pointing past the bottom of the exception stack
frame created; that is, it reflects the system stack pointer values just before
the exception occurred. In this way, the operation of the debugger facility
(through an exception) is transparent to users.
http://www.mcg.mot.com/literature
Preserving the Debugger Operating Environment

Table 4-2. Exception Vectors Used by 162Bug

Exception
Illegal instruction
Trace
TRAP #0 - #14
TRAP #15
Level 7 interrupt
Level 7 interrupt
FP Unimplemented Data
Type
1. This depends on what the Vector Base Register (VBR) is set to
in the MCchip.
2. This depends on what the Vector Base Register (VBR) is set to
in the VMEchip2.
162Bug Facility
Breakpoints (used by GO, GN, GT)
Trace operations (such as T, TC, TT)
Used internally
System calls
pushbutton
ABORT
AC Fail
Software emulation and data type
conversion of floating point data.
4
4-11