ST Nucleo vs Nordic DK vs ESP32 DevKit: Which BLE Dev Board to Buy First

You’ve spent an hour on Reddit. You’ve opened 14 browser tabs. You’ve read a 2022 thread where half the replies say “just get a Nordic DK” and the other half say “ESP32 does everything for $8.” Then someone in the comments recommends an ST board you’ve never heard of, and two people argue about Zephyr for 30 replies.

You’re no closer to a decision than when you started.

Here’s the thing: this decision is simpler than the internet makes it feel. Three boards dominate BLE development in 2025: the Nordic nRF52840 DK, the ST Nucleo-WBA55CG, and the ESP32-C6 DevKit. All three are production-relevant. None is a toy. By the time you finish this article, you’ll know which one to order.

What Actually Matters When You’re Starting Out

Before looking at any specs, you need a filter. Without one, you’ll drown in MHz comparisons and flash sizes that won’t affect your first 6 months of BLE work.

Here are the 5 things that determine whether your first BLE board helps you learn or collects dust, ranked by how much they’ll affect your daily experience:

1. SDK and documentation quality. You’ll spend 80% of your time reading docs, not writing code. A bad SDK turns a weekend project into a month of frustration.
2. Community and example projects. When docs fail (and they will), you need Stack Overflow threads, forum posts, and GitHub repos to fall back on.
3. On-board debugger. If the board doesn’t include one, you’re either buying a $50+ external probe or debugging with printf over serial, and both will slow you down.
4. BLE spec coverage. Does it support BLE 5.x features? Can it run as both central and peripheral? Can you test the scenarios you’ll hit in production?
5. Price and availability. Can you actually buy it right now without a 12-week lead time?

Notice what’s missing: clock speed, flash size, number of GPIOs. Those specs matter for production. They rarely bottleneck a learning project.

The Three Contenders at a Glance

Each of these boards comes from a company that ships millions of chips into real products. The nRF52840 is probably in your Bluetooth earbuds. The STM32WBA series targets industrial IoT. The ESP32 is everywhere from smart plugs to agricultural sensors.

The real question is which ecosystem will teach you BLE fastest.

Nordic nRF52840 DK: The BLE Specialist

Nordic built its entire business around BLE. That focus shows up everywhere.

The SDK (nRF Connect SDK) is built on top of Zephyr RTOS and designed BLE-first. Every example project, every API call, every configuration option assumes you’re building a BLE application. You aren’t fighting the framework to do what you want.

Documentation is where Nordic really pulls ahead. Their DevAcademy is a free, structured course that walks you through BLE concepts using this exact board. Lesson by lesson, you go from blinking an LED to building a custom GATT service (GATT is the protocol BLE devices use to expose data to each other). It’s the closest thing to a college course that exists for BLE firmware.

The community on Nordic DevZone is the largest BLE-specific developer forum around. Questions get answered, often by Nordic engineers themselves.

The board ships with a Segger J-Link debugger built in. You plug in USB, launch your IDE, and you’re setting breakpoints within minutes.

The honest gotcha: Zephyr’s build system will confuse you. The west tool and CMake-based configuration feel alien if you’re coming from Arduino or bare-metal Makefiles. Budget a day just to get your first project compiling. It’s a real speed bump, but you only hit it once. If you’re curious about the Zephyr ecosystem around Hubble devices, there’s a Zephyr RTOS reference application worth poking through.

Best for: Someone whose primary goal is learning BLE deeply, building skills that transfer directly to production firmware roles.

ST Nucleo-WBA55CG: The STM32 Add-On

If you’ve already spent time with STM32 chips (and a lot of engineering programs use them), the Nucleo-WBA55CG lets you add BLE without learning a completely new ecosystem.

STM32CubeMX works with the WBA series. You can pin-map, clock-configure, and generate initialization code the same way you would for any other STM32. The BLE stack bolts on through STM32CubeWBA, which provides example projects for common profiles: heart rate, generic access, custom services.

The ST-Link V3 debugger is on the board. Setup is smooth if you already have STM32CubeIDE installed.

Here’s where it gets thinner: BLE-specific documentation from ST is adequate but not as tutorial-oriented as Nordic’s. You’ll find application notes like AN5928 and reference code, but fewer step-by-step BLE resources aimed at beginners. The broader STM32 community is enormous, but the BLE-focused subset around the WBA series is smaller. The WBA line only launched in 2023, so community-generated examples, blog posts, and Stack Overflow answers are still catching up.

Best for: Engineers already working with STM32, or building a product that will ship on an ST chip. Adding BLE to existing STM32 knowledge is a smart, efficient move.

ESP32 DevKit (C3/C6): The Budget Wildcard

At $5 to $10, an ESP32-C6 DevKit costs less than lunch and gives you Wi-Fi 6 plus BLE 5.3 on a single chip. That’s a good deal.

ESP-IDF, the official SDK, is FreeRTOS-based and well-documented for Wi-Fi. The BLE stack uses Apache NimBLE, which is capable but clearly secondary in Espressif’s ecosystem. BLE documentation exists and is improving, but you’ll notice the gap compared to Nordic. Tutorials tend to be shorter, examples fewer, edge cases less covered.

The community is massive, but most ESP32 BLE content you’ll find online uses the Arduino wrapper, which hides the actual BLE stack behind convenience functions. That’s great for getting a demo running in 20 minutes. It’s bad for understanding what’s happening underneath, which is what employers actually care about.

The biggest friction point: most ESP32 dev boards don’t include a debugger. You’ll either buy an external JTAG adapter or rely on serial printf debugging. For a beginner trying to understand BLE state machines and connection events, not being able to set breakpoints and inspect memory is a real handicap.

Best for: Budget-constrained prototypers who need Wi-Fi and BLE on the same board, or hobbyists who want to experiment quickly without spending much.

Head-to-Head: The Scored Matrix

No board wins every category. The ESP32 dominates on price. The Nucleo holds its own on debugger and BLE spec coverage. But when you weight the criteria by what matters to a beginner, the gap is wide.

The Verdict: Buy the nRF52840 DK

If your primary goal is to learn BLE firmware development, and you don’t have a specific reason to pick one of the others, order the nRF52840 DK. It costs about $40.

It’s not the cheapest. It doesn’t have Wi-Fi. The build system will annoy you on day one. Buy it anyway.

You’ll spend less total time getting from zero to a working BLE project that you actually understand. Nordic’s documentation, community, and BLE-first SDK design strip away friction at every step after the initial setup. And the skills you build (Zephyr RTOS, nRF Connect SDK, BLE protocol internals) transfer directly to production work. Companies ship products on Nordic chips. A lot of them.

If you later need to connect BLE devices to a satellite or terrestrial network, the Hubble Device SDK supports Nordic-based hardware, so you won’t be starting from scratch.

Here’s a concrete order of operations: buy the DK, complete Nordic DevAcademy Lessons 1 through 4, build a custom GATT service that sends real sensor data, and then decide if you need to explore other platforms. That path takes most people 2 to 4 weeks of evening/weekend work. At the end of it, you’ll have a working project and a real understanding of BLE.

When to Pick One of the Others

Pick the Nucleo-WBA55CG if your job already uses STM32, or if the product you’re building will ship on an ST chip. Learning BLE on the same platform you’ll deploy on saves you a painful port later.

Pick the ESP32-C6 DevKit if you need Wi-Fi and BLE on the same board from day one, your budget is under $10, or you’re building a quick proof-of-concept where BLE depth doesn’t matter yet.

Close the Tabs and Start Building

The difference between engineers who learn BLE and those who don’t isn’t which board they bought; it’s whether they stopped researching and started building. The nRF52840 DK is the best default. But a Nucleo or ESP32 in your hands, running your code, beats a Nordic DK sitting in your Digikey cart for another two weeks.

Order a board. Build something that sends a byte over BLE. Everything else follows from that.

Hubble Network connects BLE devices directly to satellite, eliminating terrestrial infrastructure entirely. See how it works →