![Infineon OPTIREG TLF30681QVS01 Скачать руководство пользователя страница 64](http://html1.mh-extra.com/html/infineon/optireg-tlf30681qvs01/optireg-tlf30681qvs01_manual_2055183064.webp)
7.4
Interrupt generation (INT signal)
A dedicated interrupt generation block is implemented which is handling requests from independent sources to
generate an interrupt. The different requesters are as follows:
•
State machine in case:
-
A requested state transition has not been performed successfully
-
A requested state transition has been performed successfully, the microcontroller may only send
(additional) SPI commands after an interrupt event has been generated by the system. The purpose of
the interrupt event is to inform the microcontroller that a state transition has been performed
successfully and that the system can perform SPI communication at full SPI speed.
•
Watchdog, an interrupt request is generated if the watchdog is not serviced properly and configured in a
way to allow service errors to occur, i.e. an error counter threshold value of more than 2 is configured. In
this case an interrupt is generated only if the error counter threshold is not exceeded due to this error
•
Error pin monitoring, an interrupt request is generated if the error pin monitoring block detects an error
and is configured in a way to allow occurrence of this error for a certain amount of time (recovery delay
action enabled). In this case an interrupt is requested if an error is detected by the error pin monitoring and
the recovery delay has not expired
•
Monitoring Block, an interrupt request is generated based on the defined system reaction.
•
Overtemperature warnings and over temperature shutdown of communication LDO.
•
Overcurrent conditions of voltage reference or standby LDO.
•
SPI block in case an SPI error has occurred.
•
Double bit error in the protected configuration.
The device generates an interrupt to inform the connected microcontroller that a non-severe event has
occurred. This allows the microcontroller to take proper action based on the source of the interrupt. A single
interrupt line exists, which is high on default. All Internal interrupt sources are enabled by default and cannot be
disabled.
An interrupt is signaled by pulling the interrupt line low for at least
t
INT
(interrupt min. pulse width) after an
internal interrupt condition occurs. The interrupt line will be driven high if all of the
register flag(s) has/
have been cleared via SPI operation earliest after
t
INT
has expired but latest after
t
INTTO
has expired.
Special cases:
•
If an interrupt is signaled by pulling INT low and not all interrupt status flags are cleared by the
microcontroller within
t
INTTO
, the INT will stay low until
t
INTTO
has expired, but no additional interrupt will
be generated. Information about a pending interrupt event can be derived via the INTMISS status flag. This
status flag is cleared each time the interrupt line is driven low.
•
If an interrupt is signaled by pulling INT low and an additional bit is set in the
register interrupt flag
after the interrupt bits have been read by the microcontroller and this outdated information is used to clear
the interrupt flags, the interrupt line will stay low until
t
INTTO
has expired, but no additional interrupt will be
generated. Information about a pending interrupt event can be derived via a status flag
•
After releasing the interrupt line to high, the interrupt line will stay high for at least
t
INTTO
regardless if any
additional internal interrupt condition has occurred or not. If a new interrupt event occurs during the delay
time out (
t
INTTO
), this will be signaled by generating a new pulse after the delay time out
t
INTTO
All interrupt sources can only be cleared by a "write-1-to-clear" (w1c) SPI operation, i.e. writing a logic one to
the corresponding bit(s) in the interrupt register will clear the event
Interrupt events are organized in a two level approach. The first level (interrupt flag) provides information
about different groups of interrupt events. The second level (status flags) provides detailed information about
which particular event(s) generated the interrupt. To service an interrupt one would only need to write the
interrupt flag register. The status flag registers are only meant to provide detailed information. However all
status flags can be cleared as well
OPTIREG
™
PMIC TLF30681QVS01
Power management IC
Microcontroller interface and supervisory functions
Datasheet
64
Rev. 1.0
2020-04-08