Choosing a Microcontroller: Cores, Memory and Peripherals

Microcontroller selection is often driven by familiarity or by the fastest core in the budget. Neither is a good guide. The part has to provide the right peripherals in the right numbers, enough memory with room to grow, the power modes the product needs and a supply that will last. The core matters, but usually less than these. This article sets out how to compare candidates systematically.

At a glance

Cortex-M0+
Arm’s smallest mainstream core, with a two-stage pipeline built for low power and cost.
Cortex-M4
Adds DSP instructions and an optional single-precision floating-point unit.
Cortex-M33
An Armv8-M core with optional TrustZone security, DSP extension and FPU.
RISC-V
An open instruction set now offered in microcontrollers by several vendors.

The problem

The most common late surprise is running out of something: flash for an update image, RAM for a communications stack, a second SPI port or a timer channel. Pin multiplexing makes this worse, because two peripherals that exist on the chip may share the same pins.

The second is power. A fast core with high run current can still suit a battery product if it sleeps well, while a slow one with poor sleep modes may not.

Map every interface to a pin before choosing the part. The feature list does not tell you what fits at the same time.

Sizing memory and pins

Estimate flash and RAM from the firmware components: stacks, libraries, buffers and application code. If over-the-air updates are planned, a dual-slot scheme needs roughly twice the application space. Leave generous headroom, because firmware grows over a product life and moving to a larger part late can mean a new package.

Use the vendor’s pin configuration tool to assign every peripheral, the debug pins and wake-up inputs in the intended package. This is the step that reveals conflicts, and it takes an hour compared with a board respin.

What good looks like

List the required peripherals with counts, the memory estimate with headroom, the power modes, the temperature range and any security needs.

Shortlist parts that meet them, then check pin assignments, errata sheets, tool support and lifecycle status for each.

Prototype the riskiest function on an evaluation board before committing the layout.

Common Arm Cortex-M cores
CoreArchitectureNotable features
Cortex-M0+Armv6-MSmall gate count, very low power
Cortex-M3Armv7-MHardware divide, richer instruction set
Cortex-M4Armv7E-MDSP instructions, optional single-precision FPU
Cortex-M7Armv7E-MSuperscalar, caches, optional double-precision FPU
Cortex-M23Armv8-M BaselineSmall core with optional TrustZone
Cortex-M33Armv8-M MainlineOptional TrustZone, DSP extension and FPU
From Arm’s published core descriptions. Optional features depend on how each vendor configures the core.
Pipeline depth by core
stages
Cortex-M0+2
Cortex-M33
Cortex-M43
Cortex-M333
Cortex-M76
Number of pipeline stages in each core, from Arm documentation.

What it changes

Firmware Headroom

Memory sized with margin leaves room for features and updates.

No Pin Conflicts

Every interface is assigned before the schematic is drawn.

Right Power Profile

Sleep and run currents suit the product’s duty cycle.

Room to Grow

A family with pin-compatible larger variants allows later upgrades.

Where to go next

Read the errata sheet before committing. Silicon bugs in a peripheral you depend on are better found on paper.

Check the toolchain, debug probe and middleware support. A capable chip with poor software support costs development time.

Problems this prevents

  • Running out of flash for update images
  • Peripherals that share the same pins
  • Silicon errata found during integration
  • A respin to move to a larger package

Discuss your project

Email support@aavico.com or use Get in Touch when the website finishes loading.