Black Magic Debug

Black Magic Debug is a JTAG/SWD debugger for embedded microcontrollers, built for developers who want direct control of their build and test toolchains. It is most compelling for professional ARM- and RISC-V-focused embedded teams that already have, or are prepared to buy, compatible probe hardware. The software costs nothing, but the hardware and setup requirements make it a specialist tool rather than a universal debugger.

Overview

Black Magic Debug puts a GDB server in its firmware, so it can identify a connected target automatically without target-specific configuration scripts. In practice, that removes a common layer of board setup and leaves engineers to manage their own compiler, build system and testing environment. Remote debugging is supported, and the project describes processor support for ARM Cortex-M, ARM Cortex-A and RISC-V microcontrollers.

The usual probe appears to the host as a standard USB CDC ACM virtual serial device. Linux and macOS therefore need no special probe driver, while Windows, Linux and macOS are all supported host environments. Hardware availability deserves attention: Black Magic Probe V2.3 is active, whereas several older probe models are legacy and no longer in production.

Key features

Core debugging work is covered by watchpoints, flash-memory breakpoints, memory and register inspection, and flash programming. These tools are useful for isolating data changes, stopping execution around nonvolatile code and examining the processor when a firmware fault is difficult to reproduce. Automatic target detection makes those functions quicker to bring up on supported hardware than a workflow that depends on a separate configuration script for every target.

Semihosting and host I/O provide a route for target-side interaction with the host, while Serial Wire Output supports target tracing or output where the processor and board expose it. USB DFU firmware upgrades give compatible probes an update path without replacing the device. Documentation includes usage guidance for PlatformIO and STM32CubeIDE, so teams using either environment have a clearer starting point than those assembling an entirely undocumented integration.

The project can also be compiled as a desktop application. That mode can use BMP, ST-Link, FTDI-MPSSE, SEGGER J-Link and CMSIS-DAP adapters, which broadens the hardware choices and can speed BMP development because no firmware upload is needed. The trade-off is slower programming than with the dedicated probe-oriented setup, so it is less attractive when repeated flashing speed is central to the workflow.

Pricing

Black Magic Debug software — free. The free plan includes the JTAG/SWD debugger for embedded microcontrollers, with no paid tier or renewal commitment described. Free refers to the software; getting started still requires a Black Magic Probe and a suitable toolchain for the target processor. Budget for that probe and the surrounding development hardware before treating the zero software price as a complete solution.

Platforms

Host support covers Windows, Linux and macOS. The target side is aimed at ARM Cortex-M, ARM Cortex-A and RISC-V microcontrollers, with remote debugging available. Linux and macOS users benefit from the probe's CDC ACM interface without special drivers. The desktop application offers additional adapter compatibility, but its slower programming speed is a meaningful limitation for frequent firmware deployment.

Who it's for

This is a strong fit for professional embedded developers who want ownership of their build systems, toolchains and test environments, especially when working with supported Cortex-M, Cortex-A or RISC-V targets. It also suits teams that value an open-source probe workflow and need GDB-based remote debugging across multiple desktop operating systems.

It is a poor match for someone seeking a purely software debugger, because a compatible probe and target toolchain are prerequisites. Buyers looking at older second-hand probes should verify the model carefully, since legacy hardware is no longer in production. If rapid, repeated programming matters more than adapter flexibility, the desktop-app mode's slower flashing is another reason to choose a different arrangement.

Pros and cons

• Pros: automatic target detection avoids target-specific scripts; watchpoints, flash breakpoints, memory/register inspection and programming cover the main embedded-debug cycle; semihosting, Serial Wire Output and DFU upgrades extend the workflow; Windows, Linux and macOS support is broad; the software is free and open source.
• Cons: a compatible Black Magic Probe and target toolchain are still required; older probe models are legacy and out of production; programming is a little slower in standalone desktop-app mode; the feature set is focused on embedded microcontrollers rather than general desktop debugging.

Alternatives

Choose LLDB when you need a free, open-source debugger spanning Android, iOS, Linux, macOS and Windows without this probe-centered requirement. IDA Pro is the better choice for disassembly and decompilation: its free edition includes x86-32/x86-64 disassembly and two cloud decompilers, while IDA Pro Essential costs $1,099.00.

Pick Perl Debugger for Perl programs that already compile correctly, or PonyDebugger for an iOS client and gateway server under the Apache License 2.0. pyOCD is a free, Apache 2.0 open-source project for its supported host environments. GDB is the straightforward free GNU-licensed debugger when you want the debugger itself rather than an integrated probe workflow.

FlowStorm is a free and open-source option for its supported environments. Choose OpenOCD when an open-source debugger distributed through operating-system packages or source code better fits your setup. For a wider category view, browse Debuggers.

Verdict

Choose Black Magic Debug if you are an embedded developer who wants a free, GDB-based JTAG/SWD workflow with automatic target detection and broad host support. Its main reason to choose it is the focused combination of probe debugging, programming and output features without target scripts. Look elsewhere if you do not already have compatible hardware, need a general-purpose or reverse-engineering debugger, or cannot accept slower programming in standalone-app mode.