</>EmbeddedInterview

What are the Cortex-M profiles and how do they differ?

EasyMicrocontrollers & ARM Cortex-M

Short answer: Arm's microcontroller cores range from the tiny, low-power Cortex-M0/M0+ (Armv6-M) through the mainstream Cortex-M3/M4 (Armv7-M, M4 adding DSP and an FPU) and the high-performance Cortex-M7 (caches, TCM, superscalar), to the Armv8-M cores Cortex-M23/M33 (TrustZone security) and Cortex-M55/M85 (Helium vector extension for DSP and machine learning).

Core Architecture Pipeline Notable features Typical use
M0 / M0+ Armv6-M 3 / 2 stages smallest, Thumb subset, no hardware divide, no unaligned access, optional MPU (M0+) sensors, simple control, battery devices
M3 Armv7-M 3 Thumb-2, hardware divide, bit-banding, optional MPU general-purpose control
M4 Armv7E-M 3 M3 + DSP/SIMD instructions, optional single-precision FPU motor control, audio, sensor fusion
M7 Armv7E-M 6, dual-issue I/D caches, TCM, optional double-precision FPU high-performance control, graphics, audio
M23 Armv8-M Baseline 2 TrustZone, stack limit (secure), small secure IoT endpoints
M33 / M35P Armv8-M Mainline 3 TrustZone, DSP, FPU, stack limit registers, M35P adds physical tamper resistance secure IoT, wearables
M52 / M55 / M85 Armv8.1-M 4–7 Helium (MVE) vector instructions, optional caches/TCM, PACBTI (M85) ML at the edge, DSP

Common to all Cortex-M: Thumb instruction set only, the NVIC, the same exception model, SysTick, a 4 GB memory map with standard regions, and C-friendly interrupt handling.

Related families: Cortex-R (R5, R52, R82) for real-time safety systems (disk/SSD controllers, automotive ECUs, 5G modems) with TCM, ECC and lock-step options; Cortex-A for Linux/Android application processors.

Choosing: the core is rarely the deciding factor alone; peripherals, memory, power modes, price, toolchain and vendor ecosystem usually decide which MCU you use.