Datasheet



Are there any other cross platform or free debugging options other than GDB?

If you have a Segger J-Link, you can also use Segger's OZone debugger GUI to interact with the device, though

check the license terms since there are usage restrictions depending on the J-Link module you have.

You will need to connect your nRF52 to the J-Link via the SWD and SWCLK pins on the bottom of the PCB, or if you

are OK with fine pitch soldering via the SWD header.

You can either solder on a standard 2x5 SWD header on the pad available in the board, or you can solder wires to

the SWD and SWCLK pads on the bottom of the PCB and use an SWD Cable Breakout Board, or just connect cables

directly to your J-Link via some other means.

You will also need to connect the VTRef pin on the JLink to 3.3V on the Feather to let the J-Link know what voltage

level the target has, and share a common GND by connecting the GND pins on each device.

Before you can start to debug, you will need to get the .elf file that contains all the debug info for your sketch. You

can find this file by enabling Show Verbose Output During: compilation in the Arduino Preferences dialogue box.

When you build your sketch, you need to look at the log output, and find the .elf file, which will resemble something

like this (it will vary depending on the OS

used): /var/folders/86/hb2vp14n5_5_yvdz_z8w9x_c0000gn/T/arduino_build_118496/ancs_oled.ino.elf

In the OZone New Project Wizard, when prompted to select a target device in OZone select nRF52832_xxAA, then

make sure that you have set the Target Interface for the debugger to SWD, and finally point to the .elf file above: