English
Language : 

71M6533 Datasheet, PDF (34/132 Pages) Teridian Semiconductor Corporation – Energy Meter IC
71M6533/G/H and 71M6534/H Data Sheet
FDS_6533_6534_004
Interrupt Enable
Name
Location
EX_XFER
2002[0]
EX_RTC
2002[1]
IEN_WD_NROVF 20B0[0]
IEN_SPI
20B0[4]
EX_FWCOL
2007[4]
EX_PLL
2007[5]
Interrupt Flag
Name
Location
IE_XFER
SFR E8[0]
IE_RTC
SFR E8[1]
WD_NROVF_FLAG 20B1[0]
SPI_FLAG
20B1[4]
IE_FWCOL0
SFR E8[3]
IE_FWCOL1
SFR E8[2]
IE_PLLRISE
SFRE8[6]
IE_PLLFALL
SFRE8[7]
IE_WAKE
SFRE8[5]
IE_PB
SFRE8[4]
Interrupt Description
XFER_BUSY interrupt (INT 6)
RTC_1SEC interrupt (INT 6)
WDT near overflow (INT 6)
SPI Interface (INT2)
FWCOL0 interrupt (INT 2)
FWCOL1 interrupt (INT 2)
PLL_OK rise interrupt (INT 4)
PLL_OK fall interrupt (INT 4)
AUTOWAKE flag†
PB flag†
†The AUTOWAKE and PB flag bits are shown in Table 31 because they behave similarly to interrupt flags,
even though they are not actually related to an interrupt. These bits are set by hardware when the MPU
wakes from a push button or wake timeout. The bits are reset by writing a zero. Note that the PB flag is
set whenever the PB is pushed, even if the part is already awake.
WD_NROVF_FLAG is set approximately 1 ms before a WDT reset occurs. The flag can be cleared by
writing a zero to it and is automatically cleared by the falling edge of WAKE.
Interrupt Priority Level Structure
All interrupt sources are combined in groups, as shown in Table 32:
Table 32: Interrupt Priority Level Groups
Group Members
0 External interrupt 0, Serial
channel 1 interrupt
1 Timer 0 interrupt, External
interrupt 2
2 External interrupt 1, External
interrupt 3
3 Timer 1 interrupt, External
interrupt 4
4 Serial channel 0 interrupt,
External interrupt 5
5 External interrupt 6
Each group of interrupt sources can be programmed individually to one of four priority levels (as shown in
Table 33) by setting or clearing one bit in the SFR interrupt priority register IP0 and one in IP1 (Table 34).
If requests of the same priority level are received simultaneously, an internal polling sequence as shown
in Table 35 determines which request is serviced first.
Changing interrupt priorities while interrupts are enabled can easily cause software defects. It is best
to set the interrupt priority registers only once during initialization before interrupts are enabled.
Table 33: Interrupt Priority Levels
IP1[x]
0
0
1
1
IP0[x]
0
1
0
1
Priority Level
Level 0 (lowest)
Level 1
Level 2
Level 3 (highest)
34
Rev 2