SLAAE56B November   2022  – August 2025 MSPM0G1105 , MSPM0G1106 , MSPM0G1107 , MSPM0G1505 , MSPM0G1506 , MSPM0G1507 , MSPM0G3105 , MSPM0G3106 , MSPM0G3107 , MSPM0G3505 , MSPM0G3506 , MSPM0G3507 , MSPM0H3216 , MSPM0L1105 , MSPM0L1106 , MSPM0L1227 , MSPM0L1227-Q1 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1303 , MSPM0L1304 , MSPM0L1304-Q1 , MSPM0L1305 , MSPM0L1305-Q1 , MSPM0L1306 , MSPM0L1306-Q1 , MSPM0L1343 , MSPM0L1344 , MSPM0L1345 , MSPM0L1346 , MSPM0L2227 , MSPM0L2227-Q1 , MSPM0L2228 , MSPM0L2228-Q1

 

  1.   1
  2.   Abstract
  3.   Trademarks
  4. 1MSPM0 Portfolio Overview
    1. 1.1 Introduction
    2. 1.2 Portfolio Comparison of STM32 MCUs to MSPM0 MCUs
    3. 1.3 Pin to Pin Comparison of STM32 MCUs to MSPM0 MCUs
  5. 2Ecosystem and Migration
    1. 2.1 Software Ecosystem Comparison
      1. 2.1.1 MSPM0 Software Development Kit (MSPM0 SDK)
      2. 2.1.2 CubeIDE vs Code Composer Studio IDE (CCS)
      3. 2.1.3 CubeMX vs SysConfig
    2. 2.2 Hardware Ecosystem
    3. 2.3 Debug Tools
    4. 2.4 Migration Process
    5. 2.5 Migration and Porting Example
  6. 3Core Architecture Comparison
    1. 3.1 CPU
    2. 3.2 Embedded Memory Comparison
      1. 3.2.1 Flash Features
      2. 3.2.2 Flash Organization
      3. 3.2.3 Embedded SRAM
    3. 3.3 Power Up and Reset Summary and Comparison
    4. 3.4 Clocks Summary and Comparison
    5. 3.5 MSPM0 Operating Modes Summary and Comparison
    6. 3.6 Interrupt and Events Comparison
    7. 3.7 Debug and Programming Comparison
  7. 4Digital Peripheral Comparison
    1. 4.1 General-Purpose I/O (GPIO, IOMUX)
    2. 4.2 Universal Asynchronous Receiver-Transmitter (UART)
    3. 4.3 Serial Peripheral Interface (SPI)
    4. 4.4 I2C
    5. 4.5 Timers (TIMGx, TIMAx)
    6. 4.6 Windowed Watchdog Timer (WWDT)
    7. 4.7 Real-Time Clock (RTC)
  8. 5Analog Peripheral Comparison
    1. 5.1 Analog-to-Digital Converter (ADC)
    2. 5.2 Comparator (COMP)
    3. 5.3 Digital-to-Analog Converter (DAC)
    4. 5.4 Operational Amplifier (OPA)
    5. 5.5 Voltage References (VREF)
  9. 6Summary
  10. 7References
  11. 8Revision History

Interrupt and Events Comparison

Interrupts and Exceptions

The MSPM0 and STM32G0 both register and map interrupt and exception vectors depending on the device available peripherals. A summary and comparison of the interrupt vectors for each family of devices is included in Table 3-10. A lower value of priority for an interrupt or exception is given higher precedence over interrupts with a higher priority value. For some of these vectors the priority is user-selectable, and for others, this is fixed.

In the MSPM0 and STM32G0, exceptions such as NMI, reset, and hard fault handlers are given negative priority values to indicate that these always have the highest precedence over peripheral interrupts. For peripherals with selectable interrupt priorities, up to four programmable priority levels are available on both families of devices.

Table 3-10 Interrupt Comparison
NVIC NumberSTM32G0MSPM0
Interrupt/ExceptionPriorityInterrupt/ExceptionPriority
-ResetFixed: -3ResetFixed: -3
-NMI HandlerFixed: -2NMI HandlerFixed: -2
-Hard Fault HandlerFixed: -1Hard Fault HandlerFixed: -1
-SVCall HandlerSelectableSVCall HandlerSelectable
-PendSVSelectablePendSVSelectable
-SysTickSelectableSysTickSelectable
0Window Watchdog InterruptSelectableINT_GROUP0: WWDT0/1, DEBUGSS, FLASHCTL, WUC FSUBx, and SYSCTLSelectable
1Power Voltage Detector InterruptSelectableINT_GROUP1: GPIOA/B/C, COMP0/1/2,

TRNG(1)

Selectable
2RTC and TimestampSelectableTIMG8(1)Selectable
3Flash Global InterruptSelectableUART3(1)Selectable
4RCC Global InterruptSelectableADC0Selectable
5EXTI0 and EXTI1 interruptSelectableADC1(1)Selectable
6EXTI2 and EXTI3 interruptSelectableCANFD0(1)Selectable
7EXTI4-EXTI15 interruptSelectableDAC0(1)Selectable
8UCPD1/UCPD2/USBSelectable

TIMG9(1)

Selectable
9DMA1 Channel 1SelectableSPI0Selectable
10DMA1 Channel 2 and 3SelectableSPI1(1)Selectable
11DMA1 Channel 4-6, and DMA2 Channel 1-5Selectable

SPI2(1)

Selectable
12ADC and ComparatorSelectable

CANFD1(1)

Selectable
13Timer 1 (TIM1), Break, Update, Trigger, and CommutationSelectableUART1(1)Selectable
14TIM1 Capture CompareSelectableUART4(1)Selectable
15TIM2 global interruptsSelectableUART0Selectable
16TIM3 and TIM4 global interruptsSelectableTIMG0(1)Selectable
17TIM6, LPTIM1, and DAC interruptsSelectableTIMG6(1)Selectable
18TIM6 and LPTIM2 global interruptsSelectableTIMA0(1)Selectable
19TIM14 global interruptsSelectableTIMA1Selectable
20TIM15 global interruptsSelectableTIMG7(1)Selectable
21TIM16 and FDCAN0 global interruptsSelectableTIMG12(1)Selectable
22TIM17 and FDCAN1 global interruptsSelectable

TIMG14(1)

Selectable
2312C1 global interruptsSelectable

UART5(1)

Selectable
24I2C2 and I2C3 global interruptsSelectableI2C0Selectable
25SPI1 global interruptsSelectableI2C1Selectable
26SPI2 and SPI3 global interruptsSelectable

I2C2(1)

Selectable
27USART1 global interruptsSelectable

UART7(1)

Selectable
28USART2 and LPUART2 global interruptsSelectableAES(1)Selectable
29USART 3-6 and LPUART1 global interruptsSelectable

UART6(1)

Selectable
30CEC global interruptsSelectableRTC(1)Selectable
31AES and RNG global interruptsSelectableDMASelectable
Listed interrupts are specific to the MSPM0G3519. Check the device-specific data sheet for exact specifications.

Event Handler and EXTI (Extended Interrupt and Event Controller)

The MSPM0 devices include a dedicated event manager peripheral, which extends the concept of the NVIC to allow digital events from a peripheral to be transferred to the CPU as interrupts, to the DMA as a trigger, or to another peripheral to trigger a hardware action. The event manager can also perform handshaking with the power management and clock unit (PMCU), to make sure that the necessary clock and power domain are present for triggered event actions to take place.

 Generic Event Route Figure 3-2 Generic Event Route

In the MSPM0 event manager, the peripheral that generates the event is known as a publisher, and the peripheral, DMA, or CPU that acts based on the publisher is known as the subscriber. The potential combinations of available publisher and subscriber are extremely flexible and can be used when migrating software to replace functionality previously handled by interrupt vectors and the CPU, to bypass the CPU entirely. For example, an I2C-to-UART bridge can previously have triggered a UART transmission upon receipt of an I2C STOP, using an ISR to set a flag, or load the UART TX buffer directly. With the MSPM0 Event handler, the I2C transaction complete event can trigger the DMA to load the UART TX buffer directly, and therefore eliminate the need for any action by the CPU.

See the Events section of the MSPM0G technical reference manual or the MSPM0L technical reference manual to get more details on the use of the event handler in MSPM0.

Not to be confused with the MSPM0 event handler, the STM32G0 family of devices implement an extended interrupt and event controller (EXTI), which allows for the system wake from STOP mode through configurable events from IOs or peripherals. The wakeup features of the STM32G0 EXTI can be best replicated in MSPM0 using the IO wakeup features (see the IOMUX section of the MSPM0 technical reference manuals) and GPIO FastWake (see the GPIO section of the MSPM0 technical reference manuals). If the wakeup is for a single action, the Event handler peripheral is capable of requesting necessary PMCU resources for a peripheral operation to occur, and returning to the applicable low power mode after.