how to get eclipse neon 2 to work off usb

You may need to select List All Devices from the Options menu to see the device. In order to use a Particle Programmer Shield with OpenOCD under Windows you'll need to assign the STM32 STLink device using Zadig. The Photon USB cable isn't entirely necessary because the shield can power the Photon, but since the Eclipse debug process below by default uses DFU to load the debugging code onto the Photon, it's easier if you use a direct USB connection to the Photon for that. One connects to the Programmer Shield to access the JTAG features, and the other connects directly to the Photon. You will need to use two separate micro USB cables. If you need your device to be in a breadboard while you debug you can look at using one of the other interfaces. You can also use it with an Electron, with the extra pins hanging over the edge. The Particle Programmer Shield is designed to fit the Photon. Some debuggers support SWD (Single Wire Debug) mode, JTAG mode or both to talk to the STM32 microcontroller. In this tutorial, we'll use three different debugger devices, but they all work in the same way so you can choose whatever device you prefer. This is necessary because the cloud compilers are not configured to generate debugging builds. The instructions are in the local build FAQ.

Install a gcc-arm toolchain for local building for Windows, Mac or Linux.

It provides an automated way to install local development tools and do source-level debugging without the extreme hassle of the method described below. While you can still use these instructions, a much easier way to install Particle Workbench.

Set breakpoints in code and view source.

This FAQ describes how to use Eclipse, a free IDE for Windows, Mac, and Linux, along with OpenOCD, to do source-level debugging of code running on a Particle Photon, P1, or Electron.

Debugging with Eclipse Particle Debugging with Eclipseĭebugging Particle Photon/P1/Electron code using JTAG/SWD and Eclipse

How to get eclipse neon 2 to work off usb