I don't need a debugger. I have a brand new ICD3 here for a couple
years now, which I still haven't used yet. With a logic analyzer and an
LED or two, I can diagnose issues quite well.
I was also thinking about power as that's one of the big differences
between the Pickit2 and Pickit3 (IIRC 100mA and 50mA respectively), but
I have no issues on a specific board with an 18F25K22, though when I
switch just the chip to a 26K42, it's finnicky. So not sure that power
is the issue.
I've tried fresh cables... no difference, and on one board, I have a
direct pin header that the Pickit3 plugs into... same issue.
Yes the board is very proven and has had a few revisions -- thousands of
units with a 16F872, 16F1936, 16F883, 18F25K22, and now the 18F26K42. I
went to the Pickit3 just for the 18F parts, and though the programmer
software is annoying, it worked for the 18F25K22. Just swapping to the
18F26K42 introduces a lot of connection issues and frustration.
Interesting note... the 16F883 had some finnickyness also, and I figured
out just where to press a finger on the PGC/PGD pins to get it to work
fine. I can get that to work sometimes for the PIC32 with the Pickit3,
but not always.
Yes, sometimes, removing and re-plugging in the Pickit3 and restarting
the IPE seems to help but most of the time it doesn't.
But it's 2018 and Microchip has been doing this for long enough that I
shouldn't have to deal with all of this. Hence my intention to just
find something else that works. I just want to keep it lower cost ($50
is fine) as I will get at least 3.
Cheers,
-Neil.
Post by Isaac M. BavarescoNeil, I have had debugging problems with PIC Kit 3, but very seldom
programming issues.
The most frequent problem is related to the PIC Kit not being able to
supply power to the board. The solution it to power the board with a power
supply.
The second most common problem is due to cable and connector wear and tear.
When I start getting too many failures I cut the ends of the debugging
cable and fit new connectors.
Is this board of yours an already proven design? Sometimes poor board
design can lead to debugging failures.
The PIC Kit can behave erratically after being connected to the PC for a
long time when debugging, but just programming takes very little time. When
I suspect that the debugger is starting to misbehave I just unplug it,
close the IDE and start over.
Cheers,
Isaac
Post by NeilI've been having a frustrating experience with the Pickit 3
(intermittent and finnicky connection and programming issues for some
devices) which I've googled, but have not been able to resolve after
much tinkering with drivers, resistors, and registry settings. A brand
new second Pickit 3 gives me the same issues, and so does a new device
on a new PCB. So it's time to move on.
I really miss using the Pickit 2's, but they don't support the newer
devices.
Is there anything similar is size/cost that can program the newer
devices that any of you would recommend? FWIW, I have not faith in the
Pickit 4.
Cheers,
-Neil.
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
--
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist