Choosing the Right Platform on Embedded Systems Development

MCU vs MPU — When to Use Which

Mon, 01 Jan 0001 00:00:00 +0000

MCU vs MPU — When to Use Which#

The split between microcontrollers and microprocessors is the first fork in any embedded design. An MCU like the STM32F405 integrates 1 MB of flash, 192 KB of SRAM, and dozens of peripherals onto a single chip — power on and code executes in microseconds. An MPU like the Raspberry Pi CM4 (BCM2711, quad-core Cortex-A72) needs external DDR, an SD card or eMMC for storage, and boots a full Linux kernel in seconds. These are fundamentally different computing models, and picking the wrong one either over-constrains the software or over-complicates the hardware.

Key Specs That Actually Matter

Mon, 01 Jan 0001 00:00:00 +0000

Key Specs That Actually Matter#

MCU datasheets list hundreds of parameters, but most projects are decided by a handful of specifications that interact with each other. A 200 MHz clock means little if the flash has 5 wait states and no cache. A 12-bit ADC sounds capable until the effective number of bits (ENOB) turns out to be 9.5 at full speed. Learning to read past the headline numbers and focus on the specs that constrain real designs separates productive part selection from spec-sheet paralysis.

Popular MCU Families Compared

Mon, 01 Jan 0001 00:00:00 +0000

Popular MCU Families Compared#

No single MCU family is best for everything. Each has a core strength — wireless integration, toolchain maturity, price, or community momentum — and a set of tradeoffs that make it a poor fit for certain projects. Understanding what each family does well, and where it struggles, prevents the common mistake of choosing a chip based on familiarity rather than fit.

Family Overview#

Family	Core	Clock (MHz)	Flash	RAM	Wireless	Typical Price (1K)
STM32F4	Cortex-M4F	168	256 KB–2 MB	128–256 KB	No	$3–6
STM32H7	Cortex-M7	480	128 KB–2 MB	1 MB	No	$7–12
ESP32-S3	Xtensa LX7 (dual)	240	8 MB (ext)	512 KB	WiFi + BLE 5	$2–3
nRF52840	Cortex-M4F	64	1 MB	256 KB	BLE 5.3, 802.15.4	$3–5
nRF5340	Cortex-M33 + M4	128/64	1 MB	512 KB	BLE 5.4, direction finding	$4–6
RP2040	Cortex-M0+ (dual)	133	16 MB (ext)	264 KB	No	$0.70
ATmega328P	AVR (8-bit)	20	32 KB	2 KB	No	$1.50
PIC18F	PIC (8-bit)	64	128 KB	4 KB	No	$1–2
ESP32-C3	RISC-V	160	4 MB (ext)	400 KB	WiFi + BLE 5	$1–2
CH32V003	RISC-V	48	16 KB	2 KB	No	$0.10

STM32 — The Broad Range#

ST’s STM32 line spans from the ultra-low-power L0 (Cortex-M0+, 32 MHz, sub-uA stop) to the H7 (Cortex-M7, 480 MHz, 1 MB RAM). CubeMX generates peripheral initialization code, and the HAL library covers most peripherals. The ecosystem is mature: Keil, IAR, GCC, and CubeIDE all work. The weakness is complexity — the HAL is verbose, CubeMX-generated code can be opaque, and the sheer number of part variants (over 1,000 SKUs) makes selection itself a project. Supply chain exposure became a headline issue during 2021–2023: STM32F4 and STM32H7 lead times stretched to 52+ weeks, and spot pricing for some parts exceeded 10x the normal rate. ST manufactures primarily through a small number of fabs, making the line vulnerable to single-source disruption. Designing with pin-compatible alternatives (GD32, AT32 from Artery) or maintaining a firmware HAL that can retarget to a different family provides insurance.

Packages & Solderability

Mon, 01 Jan 0001 00:00:00 +0000

Packages & Solderability#

The package a microcontroller comes in determines how the board is assembled, how prototyping works, and whether rework is feasible. A design that requires BGA reflow is not getting hand-assembled in a home lab. Conversely, choosing a DIP package for production adds unnecessary board area and limits MCU selection to a shrinking set of legacy parts. Package choice is a design constraint that affects the entire project lifecycle from first prototype to volume manufacturing.

Ecosystem & Vendor Lock-In

Mon, 01 Jan 0001 00:00:00 +0000

Ecosystem & Vendor Lock-In#

The silicon is only half the decision. The toolchain, HAL, documentation, community, and long-term supply chain behind an MCU determine whether development moves quickly or bogs down in obscure register configurations and unanswered forum posts. A technically superior chip with a broken IDE and sparse documentation costs more in engineering time than a slightly less capable part with a polished ecosystem. Vendor lock-in compounds this: firmware written against a proprietary HAL does not port to a different vendor without substantial rewriting.