Exception Vectors Used By 166Bug; Table 4-2. Exception Vectors Used By 166Bug - Motorola MVME166IG/D2 Installation Manual

Exception Vectors Used by 166Bug

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, etc) to operate.

Table 4-2. Exception Vectors Used by 166Bug

Vector
Offset
$10 Illegal instruction
$24 Trace
$80-$B8 TRAP #0 - #14
$BC TRAP #15
$NOTE Level 7 interrupt
$NOTE Level 7 interrupt
$DC FP Unimplemented Data Type Software emulation and data type
NOTE: These depend on what the Vector Base Register (VBR) is set to
in the VMEchip2.
When the debugger handles one of the exceptions listed 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.
MVME166IG/D2
Preserving the Debugger Operating Environment
Exception
Breakpoints (used by
Trace operations (such as
Used internally
System calls
ABORT pushbutton
AC Fail
conversion of floating point data.
166Bug Facility
GO GN GT
, ,
T TC TT
, ,
4
)
)
4-11