RobotGuide
Hardware selection/MCU and Domain Controller

Selection 1 / 5

MCU and Domain Controller

How to actually choose between STM32, Raspberry Pi, and Jetson

Choosing the wrong MCU costs the most rework: swap the board and the drivers, real-time validation, and mechanical parts all have to be redone. So filter by control frequency first, then decide whether you need Linux, and only then look at compute.

ModelComputeReal-timePriceGood forNot good for
STM32F4Cortex-M4 168 MHzHard real-time, 10 kHz+¥25–60Motor driving, real-time IOVision, networking
STM32H7Cortex-M7 480 MHzHard real-time, 10–20 kHz¥60–140Joint control, EtherCAT slaveRunning Linux
ESP32-S3Dual-core 240 MHz + WiFi/BLESoft real-time (WiFi will interrupt)¥15–40Wireless co-processor, telemetry, debugging1 kHz hard real-time
Raspberry Pi 54×A76 2.4 GHzNon-real-time, ms-level jitter¥600–900Host-computer prototyping, vision, teachingDirectly driving motors
Jetson Orin Nano1024 CUDA + 6×A78Non-real-time¥2200–3600Vision, VLA inference, multi-cameraHigh-frequency control
x86 industrial PCi5 / i7Non-real-time, can add an EtherCAT master card¥4000–15000Production lines, EtherCAT masterLow-power mobile platforms

Quick picks for three scenarios

You just want the joints to spin

STM32H7 + an off-the-shelf FOC driver board

Do not start by buying a Jetson: compute is overkill and real-time performance is worse than an MCU

You want vision-based grasping

Jetson Orin Nano + STM32 low-level controller

Layer it: vision on the Linux side, the 1 kHz loop on the MCU side

You want a wireless co-processor

ESP32-S3

Keep control on the main MCU; the ESP32 only does telemetry and debugging

Three easy-to-miss points