Hi - I consider the ICD3 indispensable.  LEDs and serial output ("printf=20
debugging") methods work but is definitely a building a house with only=20
hand tools approach.  IMHO...

Look at it this way, you can always use an ICD3 and still LED/printf=20
debug.  :)

J

Neil wrote:
> Getting back into some PIC dev lately, I and I can't read-back 18F46K22
> code with my trusty old Pickit 2.  The Pickit 3 standalone app is an
> apparently abandoned joke.  The MPLAB X IPE does not work either (not
> connecting).  And yes I fully erased the chip and reprogrammed it with
> all protection fuses off.  I'm thinking it's time to some updated tools
> anyway.
>
> I've traditionally not been big on debuggers/ICE's, as it seemed to
> required hardware and some software changes to account for the
> debugging, so I've generally preferred to build in a serial output for
> an LCD or even just a couple status LEDs, and the Saleae logic I got
> some years has been indispensible.  Also, some developers that have done
> coding for me also don't bother with ICD's.  But it's time I revisit this=
..
>
> Are any of you really using an ICD to its full intent and can say that
> it's useful?  Do I really need to change much of my circuit/code to use
> an ICD?  An ICD3 is only a couple hundred bucks... are there any better
> options for a bit more?  FWIW, my applications usually have a lot of
> external analog sensing and very finely timed digital interfacing, some
> with non-standard protocols. Will I be unable to properly debug any of
> this with an ICD?
>
> Cheers,
> -Neil.
>
--=20
http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.