![Infineon Technologies XC2200 User Manual Download Page 223](http://html1.mh-extra.com/html/infineon-technologies/xc2200/xc2200_user-manual_2055439223.webp)
XC2200 Derivatives
System Units (Vol. 1 of 2)
Interrupt and Trap Functions
User’s Manual
5-11
V2.1, 2008-08
ICU_X2K, V2.2
5.3
Interrupt Vector Table
The XC2200 provides a vectored interrupt system. This system reserves a set of specific
memory locations, which are accessed automatically upon the respective trigger event.
Entries for the following events are provided:
•
Reset (hardware, software, watchdog)
•
Traps (hardware-generated by fault conditions or via TRAP instruction)
•
Interrupt service requests
Whenever a request is accepted, the CPU branches to the location associated with the
respective trigger source. This vector position directly identifies the source causing the
request, with
two exceptions
:
•
Class B hardware traps all share the same interrupt vector. The status flags in the
Trap Flag Register (TFR) are used to determine which exception caused the trap. For
details, see
•
An interrupt node may be shared by several interrupt requests, e.g. within a module.
Additional flags identify the requesting source, so the software can handle each
request individually. For details, see
The reserved vector locations build a vector table located in the address space of the
XC2200. The vector table usually contains the appropriate jump instructions that transfer
control to the interrupt or trap service routines. These routines may be located anywhere
within the address space. The location and organization of the vector table is
programmable.
The Vector Segment register VECSEG defines the segment of the Vector Table (can be
located in all segments, except for reserved areas).
Bitfield VECSC in register CPUCON1 defines the space between two adjacent vectors
(can be 2, 4, 8, or 16 words). For a summary of register CPUCON1, please refer to
.
Each vector location has an offset address to the segment base address of the vector
table (given by VECSEG). The offset can be easily calculated by multiplying the vector
number with the vector space programmed in bitfield VECSC.
Table 0-2
lists all sources capable of requesting interrupt or PEC service in the XC2200,
the associated interrupt vector locations, the associated vector numbers, and the
associated interrupt control registers.
Note: All interrupt nodes which are currently not used by their associated modules or are
not connected to a module in the actual derivative may be used to generate
software controlled interrupt requests by setting the respective IR flag.