Architecture and Hardware

Embedded Development Boards: How to Choose One

What a development board is, the main types from Arduino and STM32 Nucleo to ESP32 and Raspberry Pi, and how to pick one for your project or learning goals.

On this page
  1. What is a development board?
  2. Main types of development boards
  3. Popular boards compared
  4. How to choose a development board
  5. Suggested starting points
  6. Common mistakes when picking a board

What is a development board?

A development board (dev board) is a ready-made circuit board built around a microcontroller or processor, made for writing and testing code without designing your own hardware first. It usually includes:

  • The chip itself, plus its clock crystal and supporting components
  • A voltage regulator and a power input, often USB
  • Headers or pads that expose the chip’s pins
  • A way to load code: a USB bootloader, a programming chip or a full onboard debugger
  • Often some basic I/O such as an LED, a button and sometimes sensors or a radio

Engineers use dev boards to evaluate chips and prototype products before custom hardware exists. Hobbyists and students use them as the main platform for projects. Either way, the board saves you from building the basic circuit just to get started. To see how a board’s parts fit into a complete design, see our embedded system architecture guide.

Main types of development boards

Microcontroller boards

These carry a microcontroller (MCU): a single chip with a processor core, flash, RAM and peripherals. They run one program directly on the hardware (“bare-metal”) or under a small real-time operating system. They start up almost instantly, respond predictably, and can draw very little power.

Examples: Arduino Uno, Raspberry Pi Pico, STM32 Nucleo boards, Teensy.

Wireless microcontroller boards

These are microcontroller boards whose chip includes a radio, commonly Wi-Fi, Bluetooth Low Energy, or both. They’re the usual choice for connected (IoT) projects.

Examples: ESP32 development kits, Raspberry Pi Pico W, Nordic nRF52 and nRF53 development kits, Arduino Nano ESP32.

Single-board computers

A single-board computer (SBC) uses an application processor, such as an Arm Cortex-A, with external RAM, and usually runs a full operating system like Linux. SBCs handle networking, cameras, displays, file systems and heavier software easily. The trade-offs are boot time, higher power draw and less predictable timing than a microcontroller. Our comparison of Arm Cortex-M, Cortex-A and Cortex-R cores explains the processor difference.

Examples: Raspberry Pi 4 and 5, BeagleBone Black, NVIDIA Jetson boards for AI workloads.

FPGA boards

FPGA boards carry a field-programmable gate array: reconfigurable logic you define with a hardware description language such as Verilog or VHDL. They suit high-speed parallel processing, custom interfaces and learning digital design, but they need a different skill set from microcontroller programming.

Examples: boards based on Lattice iCE40 parts, Digilent boards based on AMD (Xilinx) Artix-7 parts.

Vendor evaluation and discovery kits

Chip manufacturers sell their own boards to showcase specific parts: ST’s Nucleo and Discovery boards, NXP’s FRDM boards, TI LaunchPads, Microchip Curiosity boards, Nordic DKs and others. They’re usually inexpensive, well documented and supported by the vendor’s tools. They’re a good route into professional embedded work.

Board Chip and core Logic level Loading and debugging Notable for
Arduino Uno R3 Microchip ATmega328P, 8-bit AVR 5 V USB bootloader via Arduino IDE Huge beginner ecosystem and shields
Arduino Uno R4 Renesas RA4M1, Arm Cortex-M4 5 V USB Uno form factor with a 32-bit chip
Raspberry Pi Pico / Pico 2 RP2040 (dual Cortex-M0+) / RP2350 (dual Cortex-M33 or RISC-V) 3.3 V USB drag-and-drop; SWD pins for a debug probe Low cost, PIO blocks, MicroPython and C SDK
ESP32 DevKit boards Espressif ESP32 family 3.3 V USB-serial; some variants have built-in USB JTAG Wi-Fi and Bluetooth built in
STM32 Nucleo STM32 family, Arm Cortex-M (many options) 3.3 V Onboard ST-LINK debugger Professional toolchain, wide range of chips
Nordic nRF52840 DK nRF52840, Arm Cortex-M4F Around 3 V (see board docs) Onboard SEGGER J-Link Bluetooth LE, Thread, Zigbee
Teensy 4.x NXP i.MX RT1062, Arm Cortex-M7 3.3 V USB via Teensy Loader High clock speed, audio and USB work
Raspberry Pi 5 Broadcom BCM2712, quad Arm Cortex-A76 3.3 V GPIO Runs Linux from an SD card or other storage Full computer for vision, networking and UIs

Specifications change between board revisions. Check the current product page before buying.

How to choose a development board

Start from what you want to build or learn

  • Learning the basics (blinking LEDs, reading buttons and sensors): a board with a large beginner community, such as an Arduino or Raspberry Pi Pico.
  • Learning professional embedded development (registers, interrupts, DMA, debugging, RTOS): an Arm Cortex-M board with a real debugger, such as an STM32 Nucleo or a Nordic DK.
  • A connected device: an ESP32 board, a Pico W or a Nordic board, depending on whether you need Wi-Fi, Bluetooth LE or both.
  • Cameras, displays, networking-heavy or AI projects: a single-board computer.
  • Custom digital logic or very fast parallel I/O: an FPGA board.

Processor and performance

Match the core to the job. An 8-bit AVR is plenty for simple control. A Cortex-M4 or M33 adds hardware floating point and DSP instructions, which helps with sensor fusion, audio and motor control. Check flash and RAM sizes as well as clock speed: running out of RAM is a more common wall than running out of CPU. Our article on microcontroller memory types explains what each kind of memory is used for.

Peripherals, I/O and logic voltage

List what you need to connect, then check that the chip has enough of each peripheral: ADC channels, PWM outputs, UART, SPI, I2C, CAN, USB and so on. Then check the logic voltage. Many modern boards use 3.3 V I/O, and applying 5 V to a pin that isn’t 5 V-tolerant can damage the chip. If your sensors and modules are 5 V parts, either choose a 5 V board or plan for level shifting. Our guide to sensors, actuators and real-world interfacing covers connecting external hardware safely.

Onboard debugger

This is one of the most underrated features. An onboard debugger (ST-LINK on Nucleo boards, J-Link on Nordic DKs, and similar on many vendor kits) lets you pause the program, step through code, set breakpoints and inspect variables and registers. Boards without one can still be debugged with an external probe, such as the Raspberry Pi Debug Probe for the Pico. If you plan to learn embedded development in depth, budget for proper debugging from the start.

Toolchain, languages and ecosystem

Most embedded code is written in C or C++. Arduino sketches are C++, and vendor SDKs are mostly C. Check what the board supports:

  • Arduino IDE for quick starts and a huge library collection
  • Vendor IDEs and SDKs such as STM32CubeIDE, the Pico SDK, ESP-IDF or nRF Connect SDK
  • PlatformIO and VS Code-based setups that support many boards
  • MicroPython or CircuitPython for quick experimentation on supported boards
  • Rust support, which is growing for several chip families
  • RTOS support such as FreeRTOS or Zephyr

Good documentation and an active community often matter more than raw specs. A popular board means more tutorials, libraries and answered questions.

Power consumption

For battery projects, check the chip’s sleep currents and the board’s extras. Power LEDs, USB-serial chips and regulators can draw far more than a sleeping microcontroller. Many dev boards aren’t optimized for low power even when the chip on them is. Some vendor kits include current-measurement points for this reason.

Path to a real product

If the project might become a product, prototype on a board whose chip family you could put on your own PCB. Vendor boards built around widely available parts make this transition easier. An SBC is harder to design onto a custom board, though compute modules exist for this purpose.

Suggested starting points

  • Complete beginner: Arduino Uno or Raspberry Pi Pico.
  • Beginner wanting Wi-Fi: an ESP32 development board or Pico W.
  • Moving toward professional work: an STM32 Nucleo board with STM32CubeIDE, or a Nordic DK with nRF Connect SDK.
  • Linux and higher-level software: Raspberry Pi.

These are common, well-supported choices rather than the only good ones. Many vendors make excellent boards.

Common mistakes when picking a board

  • Buying on clock speed alone and ignoring RAM, peripherals, documentation and debugging support.
  • Ignoring logic levels and connecting 5 V modules directly to 3.3 V pins.
  • Picking an SBC for a simple control job a microcontroller would handle more simply and reliably.
  • Choosing an obscure clone with poor documentation. Clones of popular boards can work fine, but some ship with different USB-serial chips or components that need extra drivers or setup.
  • Skipping the debugger and relying only on print statements for every problem.

The complete guide to architecture and hardware

Embedded System Architecture: Hardware and Software Components
Read the guide

Keep exploring

Guides from other topics

All topics →