pyOCD is an open source Python package for programming and debugging Arm Cortex-M microcontrollers using multiple supported types of USB debug probes. It is fully cross-platform, with support for Linux, macOS, and Windows.
A command line tool is provided that covers most use cases, or you can make use of the Python API to enable low-level target control. A common use for the Python API is to run and control CI tests.
Upwards of 70 popular MCUs are supported built-in. In addition, through the use of CMSIS-Packs, nearly every Cortex-M device on the market is supported.
pyocd command line tool gives you total control over your device with these subcommands:
gdbserver: GDB remote server allows you to debug using gdb via either GNU MCU Eclipse plug-in or the console.
flash: Program files of various formats into flash memory.
erase: Erase part or all of an MCU's flash memory.
pack: Manage CMSIS Device Family Packs that provide additional target device support.
commander: Interactive REPL control and inspection of the MCU.
list: Show connected devices.
The API and tools provide these features:
- halt, step, resume control
- read/write memory
- read/write core registers
- set/remove hardware and software breakpoints
- set/remove watchpoints
- write to flash memory
- load binary, hex, or ELF files into flash
- reset control
- access CoreSight DP and APs
- SWO and SWV
- and more!
- Python 3.6.0 or later (preferred), or Python 2.7.9 or later
- macOS, Linux, or Windows 7 or newer
- Microcontroller with an Arm Cortex-M CPU
- Supported debug probe
PyOCD is functionally reliable and fully useable.
The Python API is considered partially unstable as we are restructuring and cleaning it up prior to releasing version 1.0.
The pyOCD documentation is located in the docs directory.
In addition to user guides, you can generate reference documentation using Doxygen with the supplied config file.
The latest stable version of pyOCD may be installed via pip as follows:
$ pip install -U pyocd
To install the latest prerelease version from the HEAD of the master branch, you can do the following:
$ pip install --pre -U git+https://github.com/mbedmicro/pyOCD.git
You can also install directly from the source by cloning the git repository and running:
$ python setup.py install
Note that, depending on your operating system, you may run into permissions issues running these commands. You have a few options here:
- Under Linux, run with
sudo -Hto install pyOCD and dependencies globally. (Installing with sudo should never be required for macOS.)
- Specify the
--useroption to install local to your user.
- Run the command in a virtualenv local to a specific project working set.
For notes about installing and using on non-x86 systems such as Raspberry Pi, see the relevant documentation.
pyusb and its backend library libusb are dependencies on all supported operating systems. pyusb is a regular Python package and will be installed along with pyOCD. However, libusb is a binary shared library that does not get installed automatically via pip dependency management.
How to install libusb depends on your OS:
- macOS: use Homebrew:
brew install libusb
- Linux: should already be installed.
- Windows: download libusb from libusb.info and place the DLL in your Python installation folder next to python.exe. Make sure to use the same 32- or 64-bit architecture as your Python installation. Note: due to a known issue, the current recommendation is to use libusb version 1.0.21 on Windows instead of the most recent version.
udev rules on Linux
On Linux, particularly Ubuntu 16.04+, you must configure udev rules to allow pyOCD to access debug probes from user space. Otherwise you will need to run pyOCD as root, using sudo, which is very highly discouraged. (You should never run pyOCD as root on any OS.)
See the target support documentation for information on how to check if the MCU(s) you are using have built-in support, and how to install support for additional MCUs via CMSIS-Packs.
Standalone GDB server
After you install pyOCD via pip or setup.py, you will be able to execute the following in order to start a GDB server powered by pyOCD:
$ pyocd gdbserver
You can get additional help by running
pyocd gdbserver --help.
Example command line GDB session showing how to connect to a running
pyocd gdbserver and load
$ arm-none-eabi-gdb application.elf <gdb> target remote localhost:3333 <gdb> load <gdb> monitor reset
pyocd gdbserver subcommand is also usable as a drop in place replacement for OpenOCD in
existing setups. The primary difference is the set of gdb monitor commands.
Recommended GDB and IDE setup
The recommended toolchain for embedded Arm Cortex-M development is GNU Arm Embedded, provided by Arm. GDB is included with this toolchain.
To view peripheral register values either the built-in GNU MCU Eclipse register view can be used, or the Embedded System Register Viewer plugin can be installed. These can be installed from inside Eclipse using the following software update server addresses:
- GNU MCU Eclipse: http://gnu-mcu-eclipse.sourceforge.net/updates
- Embedded System Register Viewer: http://embsysregview.sourceforge.net/update
In Eclipse, select the "Help -> Install New Software..." menu item. Then either click the "Add..." button and fill in the name and URL from above (once for each site), or simply copy the URL into the field where it says "type or select a site". Then you can select the software to install and click Next to start the process.
Please see the Developers' Guide for instructions on how to set up a development environment for pyOCD.
We welcome contributions to pyOCD in any area. Please see the contribution guidelines for detailed requirements for contributions.
To report bugs, please create an issue in the GitHub project.
PyOCD is licensed with the permissive Apache 2.0 license. See the LICENSE file for the full text of the license.
Copyright © 2006-2019 Arm Ltd and others (see individual source files)