Yes, I was looking at it earlier and am rather pleased that it contains the circuit diagram. I wonder if Bill will be making a clone if they release the firmware.
There is this link **broken link removed**
Is it $20 more just so you can debug a PIC32, or am I missing something here? Seems a bit more evolutionary, and a bump on the price to boot. Hopefully they will keep the PicKit 2 current for quite awhile longer.
I think the main advantage is speed, the PK2 is very slow when debugging whilst watching a few variables. If you view all the SFRs then expect to wait 10 seconds per step.
Mike, I know how slow the pk2 is but after quick walk-trough the pk3 ds I just got the idea it is "bit faster" nothing else... If it will reduce avg 4sec per step to 1sec per step - it is not "fast enough" imho to trigger upgrade from pk2 to pk3... for "initial" purchase maybe, but I still haven't found any reason to upgrade
I'm I'm no rush to get a PK3 aside from the reed case
All the PICs I use are supported by the PK2 / Junebug. As for speed the single stepping mode is slowed by the number of watch variables you're viewing and do you really need to see more than a handful (you can group them into sets)
If you're a serious programmer you'll probably want the very fast ICD3 (emulation is fast as it's done internally via an FPGA)
Most hobbiests / students / experimenters are still using crappy old JDM programmers and have never even used a debugger.
IMHO between the MPLAB simulator (code testing) and a debugger (I/O, real world) the PK2 is the best PIC programmers tool for less than $50
I built the Junebug as a tool designed as the programmer built for my kits & breadboarding (the 2x5 connector was chosen for reliability, durability & availability.
I built the Junebug as a tool designed as the programmer built for my kits & breadboarding (the 2x5 connector was chosen for reliability, durability & availability.