
DS4830 User’s Guide
38
I
2
C Slave Transmit Complete Interrupt
I
2
C Slave Receive Ready Interrupt
I
2
C Slave Clock Stretch Interrupt
I
2
C Slave Timeout Interrupt
I
2
C Slave Address Match Interrupt
I
2
C Slave General Call Interrupt
I
2
C Slave Receiver Overrun Interrupt
ADC Data Available Interrupt
Internal Temperature Interrupt
External Temperature 0 Interrupt
External Temperature 1 Interrupt
Sample and Hold 0 Interrupt
Sample and Hold 1 Interrupt
SPI Master Transfer Complete
SPI Master Write Collision
SPI Master Receive Overrun
When an interrupt condition occurs, its individual flag is set, even if the interrupt source is disabled at the local, module, or
global level. Interrupt flags must be cleared within the user interrupt routine to avoid repeated interrupts from the same
source.
Since all interrupts vector to the address contained in the Interrupt Vector (IV) register, the Interrupt Identification Register
(IIR) may be used by the interrupt service routine to determine the module source of an interrupt. The IIR contains a bit
flag for each peripheral module and one flag associated with all system interrupts; if the bit for a module is set, then an
interrupt is pending that was initiated by that module.
In the DS4830 MIIR registers are defined for module 1 and 2. In these modules the DS4830 provides two ways to
determine which block inside a module (for module 1 and 2 only) caused an interrupt to occur. Module 0 and 1 has
Module Interrupt Identification Registers (MIIR1 and MIIR2) that indicate which of the module’s interrupt sources has a
Kommentare zu diesen Handbüchern