Segger’s J-Link adds Microchip PIC32 to supported MCUs

March 31, 2014 // By Graham Prophet
J-Link now fully supports direct debugging via JTAG on Microchip PIC32 devices. This includes support for the IEEE 1149.2 traditional 4-wire JTAG interface and the Microchip proprietary 2-wire JTAG interface.

Debugging via 2-wire JTAG is supported on all 2-wire JTAG compliant PIC32 devices. To start using the J-Link with PIC32, the only thing required is a current J-Link model and the Microchip adapter. The J-Link is known for fast download speed into RAM and flash memory on all supported targets, which is maintained when debugging PIC32 devices.

The J-Link allows setting an unlimited number of breakpoints in flash memory: in contrast to other debug probes supporting PIC32, J-Link does not require a debug handler in flash memory. This leaves the complete flash memory available for the target application and allows debug builds of the application to run stand-alone, even without J-Link being connected.

Segger offers a free cross-platform GDB Server for J-Link which opens the GDB world to PIC32 users, allowing them to use any GDB-based debug solution (for example, emIDE and Eclipse) with J-Link. The same feature set is supported for debugging via GDB.

“The features provided by J-Link will enable customers to exploit the performance, code efficiency and integration of our 32-bit PIC32 microcontroller portfolio, to develop innovative and cost-effective solutions," says Derek Carlson, Microchip’s vice president of Development Tools.

The Segger J-Link debug probe is tool chain independent and works with free GDB-based tool chains such as emIDE and Eclipse, as well as commercial IDEs from: Microchip (MPLAB X), Atmel, Atollic, Coocox, Cosmic, Freescale, IAR, KEIL, Mentor Graphics, Python, Rowley, Renesas, Tasking and others.