English
Language : 

W83697HF_05 Datasheet, PDF (30/102 Pages) Winbond – LPC I/O
W83697HF
6.5 SMI# Interrupt Mode
6.5.1
Voltage SMI# mode
SMI# interrupt for voltage is Two-Times Interrupt Mode. Voltage exceeding high limit or going
below low limit will causes an interrupt if the previous interrupt has been reset by reading all
the interrupt Status Register. (Figure 9.6)
6.5.2
Fan SMI# mode
SMI# interrupt for fan is Two-Times Interrupt Mode. Fan count exceeding the limit, or
exceeding and then going below the limit, will causes an interrupt if the previous interrupt has
been reset by reading all the interrupt Status Register. (Figure 9.7)
High limit
Low limit
Fan Count limit
SMI#
*
*
*
*
SMI#
*
*
*Interrupt Reset when Interrupt Status Registers are read
Figure 9.6
Figure 9.7
6.5.3 The W83697HF temperature sensor 1 SMI# interrupt has two modes
(1) Comparator Interrupt Mode
Setting the THYST (Temperature Hysteresis) limit to 127°C will set temperature sensor 1 SMI# to
the Comparator Interrupt Mode. Temperature exceeds TO (Over Temperature) Limit causes an
interrupt and this interrupt will be reset by reading all the Interrupt Status Register. Once an
interrupt event has occurred by exceeding TO, then reset, if the temperature remains above the
TO , the interrupt will occur again when the next conversion has completed. If an interrupt event
has occurred by exceeding TO and not reset, the interrupts will not occur again. The interrupts
will continue to occur in this manner until the temperature goes below TO. (Figure 9.8)
(2) Two-Times Interrupt Mode
Setting the THYST lower than TO will set temperature sensor 1 SMI# to the Two-Times Interrupt
Mode. Temperature exceeding TO causes an interrupt and then temperature going below THYST
will also cause an interrupt if the previous interrupt has been reset by reading all the interrupt
Status Register. Once an interrupt event has occurred by exceeding TO, then reset, if the
temperature remains above the THYST , the interrupt will not occur. (Figure 9.9)
- 27 -
Publication Release Date: April 14, 2005
Revision2.0