MPC563XM Reference Manual, Rev. 1
Freescale Semiconductor
781
Preliminary—Subject to Change Without Notice
23.4.2
Host Interface
23.4.2.1
System Configuration
System Configuration Registers are described in
Section 23.3.2, “System Configuration Registers
”.
Detailed explanation on the configured functionalities is found throughout
, and a specification for the initial configuration sequence is found on
”.
23.4.2.2
Interrupts and Data Transfer Requests
23.4.2.2.1
Interrupt Types and Sources
Each one of the eTPU channels can be a source of two requests:
Channel Interrupt
request and
Data
Transfer Request
. Channel Interrupts are targeted to a Host CPU. Data Transfer Requests may be targeted
to a data transfer module (e.g., a DMA controller). Interrupt and Data Transfer registers are used by the
Host to enable interrupts and data transfer requests, indicate their status and service them. Interrupt and
Data Transfer requests have the same sets of registers and external signals, and are handled in the same
way. They differ only by the fact that Data Transfer Requests are also cleared by the assertion of respective
DMA completion acknowledge line. Data Transfer Requests can be used as another source for Host
interrupts at MCU integration if not used with a DMA.
NOTE
Interrupt and Data Transfer requests can be cleared even when Engines are
in Module Disable Mode, through the Global Channel Registers, and also
DMA completion for Data Transfer requests.
Channel Interrupts and Data Transfer Requests can only be issued by eTPU microcode, through one of the
Channel Control instruction fields (see
Section 23.4.9.3.10, “Channel Interrupt and Data Transfer
”).
Both Channel Interrupt and Data Transfer requests can be individually enabled for each channel.
eTPU Interrupt and Data Transfer Registers are mirrored in two organizations: grouped by Channel and
grouped by type (interrupt status, interrupt enable, data transfer status, data transfer enable). This allows
either “channel-oriented” or “bundled channel” Host interrupt service schemes, or a combination of them.
For a detailed description, refer to
Section 23.3.5, “Channel Registers Layout
.”
eTPU can also assert a
Global Exception
interrupt indicating a global illegal state. There are three possible
sources for a Global Exception:
•
Execution of an illegal instruction by the microengine (see
Section 23.4.9.5, “Illegal Instructions
This Global Exception source is flagged by the bits ILF1 and ILF2 in register ETPUMCR.
•
An SCM signature mismatch detected by the Multiple Input Signature Calculator - MISC. See
Section 23.4.10.3.1, “SCM Test - Multiple Input Signature Calculator
the bit SCMMISF in register ETPUMCR.