SPRUJD4A December 2024 – November 2025 AM62D-Q1
The following sequence should be used for the interrupt service routine.
The interrupt service routine must be aware of the requirement that the functional unlock sequence must not be written while the functional protection mechanism is already in the unlocked state. An appropriate mutual exclusion mechanism should be used to prevent that scenario between the normal operation of the device and the interrupt service routine.
The wakeup event generation logic is level-sensitive and not edge-sensitive. Attempts to clear the status of an EXT_WAKEUP interrupt event may appear to fail if debounce is enabled and the wakeup signal is still in the active state. This can happen because the event immediately occurs again after the event status has been cleared. If debounce of these signals is enabled, then the debounce interval must elapse before the wakeup event reaches the inactive level. Because the debounce interval can be several milliseconds, waiting for the event to deassert in an interrupt service routine might negatively affect system performance. An external wakeup event should be deactivated when responding to it in an interrupt service routine instead.
Clearing the EXT_WAKEUP bits in the RTC_IRQENABLE_CLR_SYS register does not prevent the external wakeup event from causing a new interrupt status in the RTC_IRQSTATUS_RAW_SYS. To keep the status in RTC_IRQSTATUS_RAW_SYS clear, you must disable the wakeup event generation in the WKUP_EN field of the RTC_GENRAL_CTL register.