How to Choose a Microcontroller (MCU) for Your Product
Choosing a microcontroller comes down to eight factors: core and performance, power budget, peripherals, connectivity, memory, ecosystem and tooling, certification and safety, and supply and longevity. Start from the application's hard requirements — real-time control, battery life, the specific interfaces you need, and any certification — then pick the smallest part that meets them with headroom to spare. The most common mistakes are under-sizing memory and choosing a part that is hard to buy at volume.
The eight selection factors
Core & performance
Match the core to the workload: Cortex-M0+/M23 for simple control, M4/M33 for DSP and crypto, M7 for heavy real-time. Clock speed matters less than having the right peripherals and enough headroom.
Power budget
For battery designs, sleep-mode current and wake strategy dominate battery life far more than active-mode efficiency. Check the specific low-power modes and retention you actually need.
Peripherals
Count the analog (ADC/DAC, op-amps), timers, motor-control, and communication interfaces (SPI/I2C/UART/CAN/USB) you need — running out of a peripheral late in design forces a costly part change.
Connectivity
Decide whether wireless is integrated (e.g., ESP32 Wi-Fi, Nordic BLE, STM32WL LoRa) or external. Integrated radios cut BOM and board area; external radios give flexibility.
Memory
Size flash and RAM for the application plus OTA (often double the firmware), a comms stack, and future growth. Under-sizing memory is one of the most common reasons for a mid-project re-spin.
Ecosystem & tooling
A mature SDK, RTOS support, debug tooling and reference designs cut development time. STM32Cube, nRF Connect SDK and ESP-IDF are strong examples.
Certification & safety
If you need functional safety or security certification (e.g., automotive ASIL, PSA Certified, medical), choose a part and vendor that already support it — retrofitting is expensive.
Supply & longevity
Confirm lifecycle/longevity commitments, multi-source options, and current availability. A technically perfect part you cannot buy in volume is the wrong part.
Popular families, and when each wins
We design with all of these — see the dedicated capability pages for when each is the right call.
STMicroelectronics STM32
Scalable general-purpose Cortex-M family for control and mixed-signal.
Espressif ESP32
Low-cost integrated Wi-Fi / Bluetooth with on-chip compute.
Nordic nRF52 / nRF91
Ultra-low-power BLE / Thread / Matter and cellular IoT.
NVIDIA Jetson
Step up to a module when the workload is real edge AI / vision.
For a specific decision, compare the silicon platforms (STM32, ESP32, nRF52) and choosing a wireless protocol.
Frequently asked questions
8-bit vs 32-bit — which microcontroller should I use?
For most new designs a 32-bit Arm Cortex-M is the better default: similar cost to 8-bit, far more performance and memory, and a richer ecosystem. 8-bit parts still make sense for the simplest, most cost-driven, ultra-low-pin-count designs, but the gap has narrowed enough that 32-bit usually wins.
What's the difference between an MCU and an MPU?
A microcontroller (MCU) integrates CPU, flash and RAM and runs bare-metal or an RTOS for deterministic real-time control. A microprocessor (MPU) needs external memory, runs an OS like Linux, and suits rich UIs, networking stacks and heavier compute. Choose an MPU when you need Linux, a display stack, or significant processing.
When do I need an edge-AI module instead of an MCU?
Small ML — keyword spotting, simple anomaly detection, basic vision — runs on an MCU with TinyML or a small NPU. When you need multi-camera vision, large models, or robotics autonomy, step up to an edge-AI module such as NVIDIA Jetson.
How much flash and RAM do I need?
Budget for the application, the connectivity/RTOS stack, and OTA updates (which often need room for two firmware images). It is common and cheap to choose a part one size up in memory to avoid a re-spin later; under-sizing is a frequent, expensive mistake.
Should connectivity be integrated into the MCU?
Integrated wireless (Wi-Fi, BLE, LoRa) lowers BOM cost and board area and simplifies certification with pre-certified modules. A separate radio gives more flexibility and lets you pick best-in-class for each function. The right answer depends on volume, cost targets and how standard your connectivity is.
Need help choosing the right MCU?
Share your requirements — power, interfaces, connectivity, volume — and our engineers will recommend a part and design the board and firmware around it.
Get an MCU recommendation