RP2040 / Pico 2
The PIO peripheral is the trick: eight programmable state machines that can generate perfectly-timed signals in hardware. Drives 16 servos, reads quadrature encoders, or bit-bangs any protocol without touching the CPU.
The role it plays
Every serious robot needs two tiers. A microcontroller owns the control loop at a fixed rate with hard deadlines, because a missed deadline is a visible jolt. A Linux or GPU board owns perception, planning and networking, because those are bursty and best-effort. Nothing balance-critical belongs on the Linux side.
Typical use: Servo arrays, encoder interfaces, custom protocols, cheap control boards.
What the numbers actually mean
The headline figure is 2× Cortex-M0+ @ 133 MHz (Pico 2: RISC-V/M33 option) (cpu), with 264 KB as the next most load-bearing number (ram). At $4 in the compute tier it sits cheap enough to prototype with and replace without regret, which is the correct way to learn a new subsystem.
How it compares
Same subsystem, closest alternatives. The primary spec column is usually the one that decides it.
| Part | Price | Primary spec | Second spec |
|---|---|---|---|
| RP2040 / Pico 2MCU | $4 | 2× Cortex-M0+ @ 133 MHz (Pico 2: RISC-V/M33 option) | 264 KB |
| Raspberry Pi 5 (8 GB)SBC, high-level brain | $80 | 4× Cortex-A76 @ 2.4 GHz | 8 GB LPDDR4X |
| Jetson Orin Nano SuperEdge GPU | $249 | 67 TOPS (INT8, sparse) | 1024-core Ampere |
| Jetson Orin NX 16 GBEdge GPU | $499 | 100 TOPS (INT8, sparse) | 1024-core Ampere |
| ESP32-S3Real-time MCU + Wi-Fi | $5 | 2× Xtensa LX7 @ 240 MHz | 512 KB SRAM + 8 MB PSRAM typical |
Where it shows up
Platforms in this atlas that use something in this class: SO-101, Open Duck Mini v2.