Jtag pinning versus ICSP

Hi,
 
Look at the PIC32 starter kits schematic.
As far as I remember, the on board PIC32 "tool CPU" uses JTAG for programming and debugging the "application" PIC32 ;=)
I mean, the PIC32 "tool CPU" (kind of "Pickit3" functionality) is connected to PC using USB device and connected to "application" PIC32 using JTAG.
This kit only operates in debugger mode even though the application CPU can execute code once the PIC32 "tool CPU" is disconnected from PC (and hence from MPLAB X).
 
Regards
 

I'm fairly sure that configuration bit only takes effect once the device is released from reset, like how any ICSP pin pair can be used for programming the device regardless of the value of the ICESEL bits.
 
By the way, there's a series of patches in the current development version of OpenOCD that are supposed to significantly increase JTAG performance for MIPS M4K cores.

andersm
By the way, there's a series of patches in the current development version of OpenOCD that are supposed to significantly increase JTAG performance for MIPS M4K cores.

 
How fast (or slow) was the previous version?  I use the 0.6.1 version (can't find any changes in the sources from the GIT) and this version is even with a JLink on 12MHz very slow.
A single step takes ages.  I see that the TCK goes at 12MHz but the queries are going in bursts of 6 mS.
 
A single step is doing a lot and at the end it is asking the reasons why it stopped with a lot of instructions writing into the jtag chain (with that low speed burst intervals).
 
 
I also tried the jlink with openocd and a MCB1700 board and that speed is also a bit disappointing if you compare it with the native segger GDB server.
Perhaps I have to much expectations or something is completely wrong here (linusb-win perhaps???)