Dronecode Probe is a generic JTAG/SWD + UART console adapter compatible with most ARM Cortex based designs and in particular with the hardware maintained by the Dronecode project.

The design is based on Black Magic Probe and is distributed under open source licenses. The full description of its features and supported targets can be found at the Black Magic Probe homepage.

The schematics and PCB sources can be found on GitHub.



  • Supported targets:
  • Embedded GDB server on the device. No host-side driver needed (this is unlike, for example, OpenOCD).
    • Loading the application into flash or RAM.
    • Real-time execution and single-stepping.
    • Hardware assisted breakpoints and read/write/access watchpoints.
    • Software breakpoints when executing from RAM.
  • Simple integration with development tools and IDE.
  • Connectors are compatible with the Dronecode Autopilot Connector Standard.
  • Optional +3.3 V power supply delivery to the target.

Some of the supported targets. See the project homepage for the full list of supported targets.

USB interface

Dronecode Probe is a composite USB device that incorporates two virtual serial port interfaces.

The first virtual serial port interface is connected to the debugger's embedded GDB server; this interface is used by the host-side debugger to interact with the target. The baud rate and other parameters of a typical serial port are irrelevant for this interface, because it has no physical representation.

The second virtual serial port interface is connected to the physical UART interface that can be used to communicate directly with the target's application (for example, this can be used to access the Serial command line interface (Serial CLI) on the target).

For example, the host may represent the debugger as follows:

  • COM3 (on Windows), or /dev/ttyACM0 (on Linux) - this is the GDB interface.
  • COM4 (on Windows), or /dev/ttyACM1 (on Linux) - this is the physical UART interface that can be used to interact with the target's application (e.g. a serial CLI).

Droneсode Probe does not require drivers when used with Windows (version 10 or newer is required), Linux, or Mac, since it uses the standard CDC-ACM USB profile. If you're using the device with GNU/Linux, be sure to check out this page which describes how to configure the access permissions correctly: Using USB devices with GNU/Linux.

The USB Vendor ID (VID) is 0x1D50, and the Product ID (PID) is 0x6018.


This section documents the available debug interfaces and their connectors, except for the micro-USB since its purpose is evident.


DCD-M debug cable (JST SM06B-SRSS-TB)

The DCD-M (pictured on the right) connector pinout is documented in the table below. It exposes both SWD and UART interfaces to the target, where UART is typically used to access the debug serial console of the target.

1INTPWRTarget power sense; also can be used to power the target.
2INUART_RXSerial input.
3OUTUART_TXSerial output.
4IN/OUTSWDIOSWD data line.
5OUTSWDCLKSWD clock line.

The connector part numbers are as follows:

NameManufacturerPart numberPitchDatasheet

BM06B-SRSS-TB (top entry), or

SM06B-SRSS-TB (side entry)

1 mmhttp://www.jst-mfg.com/product/pdf/eng/eSH.pdf

ARM Cortex M debug connector

ARM Cortex M debug cable - 2x5 pins, pitch 1.27 mm

This is the standard ARM Cortex M Debug Connector that can be seen on many other ARM debuggers.

ARM Cortex M debug connector - 2x5 pins, pitch 1.27 mm


Pixhawk v1 serial

This connector exposes only the UART interface. It can be used as a general UART port, and its pinout is compatible with the debug serial port on the Pixhawk v1 autopilot.

1Power OUT5V

Optional 5 V supply output to the target directly from USB.

Disabled by default; refer to the schematic to see what hardware modifications are required to enable it.


Not used

Not used
4INUART_RXSerial input
5OUTUART_TXSerial output

Updating the device's own firmware

Please refer to the following sources:


Hardware v2.3