pyOCD

Overview

pyOCD is a Python-based debugger, firmware programmer, and device-control API for Arm Cortex microcontrollers. It is best suited to embedded developers who want to pair GDB-based debugging with Python automation. Its range of target and workflow options is a strong fit for Cortex-M projects, provided your device’s memory map and security behavior suit the work.

Key features

The GDB server supports command-line debugging and IDE workflows, including Arm CMSIS Debugger, Cortex-Debug, and Eclipse Embedded CDT. That lets teams use familiar debugging front ends while working with a shared tool. pyOCD can program firmware and data images into internal or external flash, or load images into RAM.

The Python API gives developers a way to control targets from CI jobs and build custom test and debug tools. More than 70 common Arm Cortex-M devices have built-in support, with CMSIS Device Family Packs providing another route to target support. Pack management can install packs by device part number. The constraint is that pyOCD supports only one system memory map for all CPUs, which can cause problems when memory regions conflict or overlap.

Debugging extras include semihosting with console and file I/O, basic printf output over SWV, raw SWO streaming over TCP/IP, and Python processing of SWO events. Built-in probe plug-ins support CMSIS-DAP, Raspberry Pi Picoprobe, SEGGER J-Link, STLink, and pyOCD remote. PE Micro Cyclone and Multilink require a separate plug-in, so those probe users have an additional setup requirement.

A server and client can share debug probes over TCP/IP, including in CI configurations. Remote connections are disabled by default; enabling them without protective measures can expose the server to any internet node. Treat remote probe access as a security-sensitive setup, not an automatically safe convenience.

Target security features currently cover NXP Kinetis and Nordic nRF52 families, including built-in and CMSIS-Pack targets. Unlocking a supported locked device can require a mass erase, which erases all data on the chip. That makes pyOCD a poor choice for unlocking when preserving target contents is essential.

Pricing

pyOCD is free: its plan costs nothing and is an open-source project under the Apache 2.0 license. There is no trial to manage, and no paid tier or seat-based price is given. This makes it a straightforward option for individual developers and teams that can work within its supported target and memory-map constraints.

Platforms

pyOCD runs on Linux, macOS, FreeBSD, and Windows and requires Python 3.9 or later. The installation guide recommends installing the stable package with pip and suggests pipx for an isolated installation. Its target platform is Arm Cortex-M microcontrollers; it is not a general-purpose debugger for unrelated processor families.

Who it's for

Choose pyOCD if you work with Arm Cortex-M devices and want GDB access, flash programming, and Python-driven control in one tool, particularly when CI or custom test automation matters. It is also a sensible fit when your device has built-in support or a suitable CMSIS-Pack. Look elsewhere if your device depends on a conflicting per-CPU memory map, your locked target must retain its data during unlocking, or you cannot safely protect remote probe access.

Support channels include GitHub issues and discussions, a public Slack workspace, and a Google Groups mailing list for announcements and news.

Pros and cons

• Pro: GDB support connects command-line and named IDE workflows, letting users keep their preferred front end.
• Pro: The Python API suits CI jobs and custom test or debug tools, extending the tool beyond interactive debugging.
• Pro: Built-in support for more than 70 common Cortex-M devices plus CMSIS-Pack support gives developers multiple paths to target coverage.
• Con: One system memory map for all CPUs can cause problems with overlapping or conflicting regions.
• Con: Unlocking a supported locked target can erase all chip data, making the security feature unsuitable when data must be preserved.
• Con: Remote probe connections can expose the server broadly if enabled without protective measures.

Alternatives

For other debugger options, browse Debuggers. OpenOCD is another free, open-source option distributed through operating-system packages or source code. Choose Black Magic Debug if its JTAG/SWD debugger for embedded microcontrollers fits your setup and you have compatible probe hardware and a suitable toolchain.

GDB is a free, source-available GNU debugger for readers seeking that standalone option. LLDB is another free debugger, with support across Android, iOS, Linux, macOS, and Windows. Choose IDA Pro if you want its free x86-32 and x86-64 disassembly tier with two cloud-based decompilers, or its paid Pro Essential plan at 1099.00 USD. Perl Debugger is included with Perl and requires the program to compile correctly before debugging. PonyDebugger is a free Apache License 2.0 option with an iOS client and gateway server. FlowStorm is a free-and-open-source alternative with no money involved.

Verdict

Choose pyOCD for Arm Cortex-M work when you want GDB debugging, firmware programming, and Python-based automation without a software fee. Its strongest reason to choose it is the combination of familiar GDB integrations and scriptable target control; its strongest reasons to look elsewhere are memory-map conflicts, data-erasing unlocks, or remote-access security needs your setup cannot address.