Faster debugger than ICD-4 for PIC32?

[ricko_uk]

Hi,
I have been debugging code with an ICD4 and it is not exactly a rocket... Any suggestions for both:

a) a faster similar tool? Perhaps that uses full USB-3 speed?
b) a full in-circuit emulator (the original Microchip REAL-ICE is no longer available)?

Thank you

[fchk]

Jlink via icsp or MIPS EJTAG.

fchk
 
https://www.segger.com/products/debug-probes/j-link/technology/cpus-and-devices/microchip-pic32-support/

[westfw]

a faster similar tool? Perhaps that uses full USB-3 speed?

What exactly do you need to be faster?
I seriously doubt that the USB connection is the bottleneck (It already has HS, 400+MBbps, right?)

[ricko_uk]

Thank you both.

fchk, that pretty much answers it.

westfw, just generally, both real time debugging/stepping and programming. But I think the link above from fchk answers it.

[voltsandjolts]

Note the j-link page says:
"J-Link fully supports super-fast, direct debugging via JTAG"
So if your device is MCHIP debug pins only (no jtag) it may be just as slow as PK4?

[ale500]

MPLABX has some issues with jlink. Not all combinations of versions and firmware are compatible. At least on my jlink v9 (original), the latest firmware made it incompatible with mplabx, that was last year's latest FW. I may have had bad luck, I bricked the pickit 3 too, mplabx tried to update the fw on that too, and failed :/.
But yeahm as long as it worked (I used mplabx 3.26 at the time and the original FW on the jlink) it was faster than the pickit 3, no idea how ICD4 fears.

[ricko_uk]

Thank you all

Ale500, I got the J-32 Debug Probe sold by Microchip but made by Jlink (after speaking with Jlink I found out it is exactly the same but specific for Microchip).

It is much faster to program BUT the MPLAB reset button (that sets/keeps the target into reset mode) does not seem to work with the jlink.