SLAU929 April 2024 MSPM0C1104 , MSPM0G3505 , MSPM0G3506 , MSPM0G3507 , MSPM0L1105 , MSPM0L1227 , MSPM0L1228 , MSPM0L1228-Q1 , MSPM0L1304 , MSPM0L1305 , MSPM0L1306 , MSPM0L2227 , MSPM0L2228 , MSPM0L2228-Q1
The MSPM0 and Microchip's 8-bit AVR MCU family feature SRAM used for storing application data.
Feature | ATmega | ATtiny | MSPM0G | MSPM0L | MSPM0C |
---|---|---|---|---|---|
SRAM memory | 512 B to 1 KB | 512 B to 3 KB | 32KB to 16KB | 4KB to 2KB | 1KB |
Select devices include SRAM parity and ECC. For more details, see the device data sheet. | |||||
Access resolution | Byte | Byte | Byte, half-word (16-bits) or full word (32-bits) | ||
Parity check | No | No | Yes | Yes | No |
MSPM0 MCUs include low-power high-performance SRAM with zero wait state access across the supported CPU frequency range of the device. SRAM can be used for storing volatile information such as the call stack, heap, and global data, in addition to code. The SRAM content is fully retained in run, sleep, stop, and standby operating modes, but is lost in shutdown mode. A write protection mechanism is provided to allow the application to dynamically write protect the lower 32KB of SRAM with 1KB resolution. On devices with less than 32KB of SRAM, write protection is provided for the entire SRAM. Write protection is useful when placing executable code into SRAM as it provides a level of protection against unintentional overwrites of code by either the CPU or DMA. Placing code in SRAM can improve performance of critical loops by enabling zero wait state operation and lower power consumption.