SLAU962A December 2025 – June 2026 MSPM33C321A , MSPM33C321A-Q1
Peripherals are configured to asynchronously assert a hardware request to the SYSCTL for a fast clock source when the device is operating in STANDBY mode. This mechanism for applications where the ULPCLK tree is sourced from LFCLK (at 32kHz), but a faster SYSOSC (at 4 MHz) is temporarily needed to quickly handle a peripheral event (for example, a timer IRQ or GPIO IRQ) or peripheral activity (such as serial communication or GPIO toggle validation thriugh the glitch filter).
Asynchronous fast clock requests are also useful for scenarios where the device is running in STANDBY1 mode. In STANDBY1 (when STOPCLKSTBY is set), the ULPCLK and LFCLK are disabled to all peripherals except for a few TIMG8_x, leaving TIMG8_x and the RTC as the only clocked peripherals. To wake up the device from this state where the bus clock (ULPCLK) is disabled, a TIMG8_x or RTC interrupt request forces an asynchronous fast clock request to wake the device to RUN mode. Other peripherals can also wake the device from this state if support for detecting an asynchronous event (for example GPIO, comparator, and serial interfaces) is described.
Asynchronous fast clock requests temporarily provide peripherals with bus clock ( ULPCLK), sourced from the SYSOSC, for the duration of the request. MFCLK, if enabled for use, is also enabled during the asynchronous request.
When configured, SYSCTL responds to a peripheral fast clock request in the following way:
After the configuration above is applied, values are held for the duration of time that the asynchronous request remains asserted plus approximately 1µs after the request is removed. The system then returns to the configuration which existed before the fast clock request, provided the CPU did not change the configuration during the request.
Asynchronous fast clock requests are ignored and results in no effect on the device configuration if any of the following are true:
The RTC, TIMG8_x, GPIO, I2C, and UART peripherals all provide support for generating an asynchronous fast clock request. The purpose, request source, and configuration requirements for these peripherals are given in Table 2-14.
| Peripheral | Purpose | Request Source | Configuration |
|---|---|---|---|
| RTC (if present) | Fast CPU wake from RTC event | RTC IRQ to CPU | An RTC IRQ event always generates an asynchronous fast clock request when the device is in STANDBY1 mode; this is needed to wake the device as the main ULPCLK is disabled to reduce power consumption. The RTC can also be configured to generate an asynchronous fast clock request in any operating mode by clearing the BLOCKASYNC bit in the RTC CLKCFG register; this provides the lowest latency RTC event response. |
| TIMG8_x | Fast CPU wake from TIMGx event | TIMGx, IRQ to CPU | An IRQ event from TIMG8_x generates an asynchronous fast clock request when the device is in STANDBY1 mode and the corresponding IMASK interrupt is set in the TIMG8_x registers. This is needed to wake the device as the ULPCLK is disabled to reduce power consumption. |
| GPIO | Fast CPU wake from GPIO event | GPIO activity | The GPIO generates an asynchronous fast clock request through the GPIO configuration registers. This is for applications where GPIO wake from STANDBY mode is desired, as the fast clock request results in the GPIO digital glitch filters running at SYSOSC base frequency. In addition to configuring the GPIO registers to request the fast clock, the BLOCKASYNCALL bit must be cleared in the SYSOSCCFG register to allow the request to propagate. |
| I2C | Temporarily use fast clock for bit clock generation | I2C activity | I2C activity generates an asynchronous fast clock request when the BLOCKASYNC bit is cleared in the CLKCFG register of the respective I2C peripheral. |
| UART | Temporarily use a fast clock for baud rate generation | UART activity | UART activity generates an asynchronous fast clock request when the BLOCKASYNC bit is cleared in the CLKCFG register of the respective UART peripheral. |
The logic for asserting a fast clock request is given in the following figure.