> For the complete documentation index, see [llms.txt](https://px4.gitbook.io/px4-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://px4.gitbook.io/px4-user-guide/development/debug/gdb_debugging/probe_jlink.md).

# JLink Probe

The [J-Link debug probe](https://www.segger.com/products/debug-probes/j-link/) is a closed-source, commercial hardware probe which supports almost all ARM Cortex-M devices. You need to install the [J-Link drivers](https://www.segger.com/downloads/jlink/) for this probe to work:

```sh
# Ubuntu
wget --post-data "accept_license_agreement=accepted" https://www.segger.com/downloads/jlink/JLink_Linux_x86_64.deb
sudo dpkg -i JLink_Linux_x86_64.deb
# macOS
brew install segger-jlink
```

Once installed, you can start the server using:

```bash
JLinkGDBServer -if swd -device STM32F765II
```

It might then prompt you to update the JLink which is recommended, and then to specify which device it is communicating with. Check the docs of your autopilot for the specific device.

Once that's done, the GDB server should be start listening on port `2331`, e.g. like so:

```bash
Checking target voltage...
Target voltage: 3.28 V
Listening on TCP/IP port 2331
Connecting to target...
Connected to target
Waiting for GDB connection...
```

You can now start GDB with the exact elf file that is currently flashed on the autopilot (in a separate terminal):

```bash
arm-none-eabi-gdb build/px4_fmu-v5_default/px4_fmu-v5_default.elf -ex "target extended-remote :2331"
```

And now you should be connected.

To use an IDE instead, see the instructions for [Eclipse](/px4-user-guide/development/debug/eclipse_jlink.md) or [VSCode](/px4-user-guide/development/getting_started/dev_env/vscode.md#hardware-debugging). See the [Embedded Debug Tools](https://pypi.org/project/emdbg/) for more advanced debug options.

### Segger JLink EDU Mini Debug Probe

The [Segger JLink EDU Mini](https://www.segger.com/products/debug-probes/j-link/models/j-link-edu-mini/) is an inexpensive and popular SWD debug probe. The probe's connector pinout looks like the image below (connect to this using an ARM 10-pin mini connector like [FTSH-105-01-F-DV-K](https://www.digikey.com/products/en?keywords=SAM8796-ND)).

![connector\_jlink\_mini.png](https://4155462212-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LArEa7z2SPawfl3HpCD%2Fuploads%2Fgit-blob-3ae1a7501a1df43113aec5fe98a7b34291764b8f%2Fconnector_jlink_mini.png?alt=media)

The pin mapping to connect the J-Link Edu Mini to [Pixhawk Debug Mini](/px4-user-guide/development/debug/gdb_debugging/swd_debug.md#pixhawk-debug-mini) is shown below.

| Pin | Signal     | JLink |
| --: | ---------- | ----: |
|   1 | **VREF**   |     1 |
|   2 | Console TX |       |
|   3 | Console RX |       |
|   4 | **SWDIO**  |     2 |
|   5 | **SWDCLK** |     4 |
|   6 | **GND**    |  3, 5 |

Note that none of the JLink debug probes have a built in serial connection, so you need to connect the console separately.