SWCU192 November 2021 CC1312R7 , CC1352P7 , CC2652P7 , CC2652R7
20.3.2.8 Wake-Up Event Handling
Figure 20-9 shows that the Sensor Controller implements an 8-bit event interface and an 8-bit vectorized wake-up event interface.
Figure 20-9 SCE Wake-Up and Event InterfaceThe AUX_SYSIF:VECCFGn registers map each of the vector inputs to a selectable wake-up event (see Section 20.8.9). Table 20-17 lists the possible wake-up events.
| Event Mapping | Value | Description |
|---|---|---|
| NONE | 0 | Disable vector input |
| PROG_WU0 | 1 | AUX_SYSIF:WUFLAGS.PROG_WU0 |
| PROG_WU1 | 2 | AUX_SYSIF:WUFLAGS.PROG_WU1 |
| PROG_WU2 | 3 | AUX_SYSIF:WUFLAGS.PROG_WU2 |
| PROG_WU3 | 4 | AUX_SYSIF:WUFLAGS.PROG_WU3 |
| SW_WU0 | 5 | AUX_SYSIF:WUFLAGS.SW_WU0 |
| SW_WU1 | 6 | AUX_SYSIF:WUFLAGS.SW_WU1 |
| SW_WU2 | 7 | AUX_SYSIF:WUFLAGS.SW_WU2 |
| SW_WU3 | 8 | AUX_SYSIF:WUFLAGS.SW_WU3 |
| AON_RTC_CH2_DLY | 9 | AUX_EVCTL:EVSTAT2.AON_RTC_CH2_DLY |
The Sensor Controller executes the sleep instruction when the wake-up event interface is properly configured. The sleep instruction halts instruction execution, freezes the internal state, and clock-gates the Sensor Controller until one or more wake-up inputs are set. Instruction execution will then resume from the vector address corresponding to the wake-up input of highest priority. Highest priority is assigned to vector 0 and priority decreases linearly down to vector input 7, as listed in Table 20-18.
| Wake-Up Input | Handler Address | Priority |
|---|---|---|
| 0 | 0x0 | Highest |
| 1 | 0x2 | |
| 2 | 0x4 | |
| 3 | 0x6 | |
| 4 | 0x8 | |
| 5 | 0xA | |
| 6 | 0xC | |
| 7 | 0xE | Lowest |
If one or more wake-up inputs are already set, the sleep instruction will immediately cause the Sensor Controller to execute from the vector address of the highest priority.
Comparing the wake-up events listed in Table 20-17 with Figure 20-9 shows that all the possible wake-up events except AON_RTC_CH2_DLY can also drive the AUX domain wake-up event. The AUX domain wake-up event is driven by:
- Four programmable AUX wake-up events can configure the following:
- Event source, see the AUX_SYSIF:PROGWUnCFG.WU_SRC registers in Section 20.8.9.
- Polarity, see the AUX_SYSIF:PROGWUnCFG.POL registers in Section 20.8.9.
- Level- or edge-selectivity, see the AUX_SYSIF:WUFLAGSCLR register in Section 20.8.9.
- Four software events, see the AUX_SYSIF:SWWUTRIG register in Section 20.8.9.
The System CPU uses these events to perform handshaking with the Sensor Controller.
Hence, the Sensor Controller will typically:
- Configure one or more programmable of the AUX wake-up events
- Configure the Sensor Controller wake-up vector interface
- Request Power-Down operational mode
- Execute the sleep instruction
- Wake up:
- Request Low-Power or Active operational mode
- Clear the wake-up flag
- Perform a task and possibly notify the System CPU
- Enable an AUX wake-up event
- Request Power-Down operational mode
- Execute sleep instruction
The requested system resources during sleep instruction are minimal, which lowers the overall system power consumption. Upon AUX wakeup, the system power controller externally forces Low-Power mode or Active AUX operational mode. The Sensor Controller must request the same operational mode before it clears the wake-up flag. For further details on AUX operational mode switching, see Section 20.2.