Electron programmer shield compatibility for JTAG debugging

Is the programmer shield in the Particle Store compatible with the Electron?

From the store:

Designed for use with the Photon, backwards compatible with the Core.

Doesn’t say anything about the Electron…

Also, if I were to buy one of these shields and adapt it for use with the Electron, would I simply follow the instructions posted in the forums? For example here: Local development and gdb debugging with NetBeans, a step by step guide

It would appear that that guide was written for use with the ST-Link (not the programmer shield). Is the programmer shield compatible with Netbeans debugging? If not, is the only IDE that is compatible with the programmer shield the WICED Eclipse-Based IDE?

Are there any other guides on debugging and creating a local build environment with Particle products? Right now it seems like there is not much info on the Particle sites about this, maybe because all the people who delve into that world already have lots of experience with this kind of thing and therefore don’t ask questions?

UPDATE:

Rickkas has written an awesome guide on how to use JTAG tools with the Electron. You can find it here:

https://docs.particle.io/faq/particle-tools/jtag/electron/

If you can wait a few weeks, there will be much more information available. I’m writing the guides debugging with JTAG and SWD right now.

3 Likes

Amazing. You the man. :hamster:

1 Like

I think there is a tutorial by @jvanier.

Since the JTAG/SWD pins are on the same spot on both device types you can use the Photon Programmer Shield just the same with the Electron.

1 Like

Thanks Scruffr!

Can I use a GUI debugger like Netbeans with the Particle Programming Shield, or am I limited to command line OpenOCD debugging (sifting through lines of assembly code)?

OpenOCD is the interface to the hardware, it could be the programmer shield or a JTAG or SWD USB device. It can then be used either to access the flash or interface to GDB.

Once you have the GDB Interface you can use either the command line source debugger or use an IDE that can interface to GDB like Eclipse or Netbeans.

2 Likes