Hi Matt,



You could "lash up" a header cable of your own quite easily, I made a break=
out cable for mine when I=20

had a dozen chips to program for a customer a little while back.



if you can't find the docs for the ICD3, here's a link to the quick guide.



http://ww1.microchip.com/downloads/en/devicedoc/ds-51765c.pdf



(sorry if I'm telling you things you already know).



-Jim





On Tue 28/05/13  9:50 AM , Matt Rhys-Roberts matt.rhys-roberts@envinsci.co.=
uk sent:

> On 24/05/13 14:40, Jan-Erik Soderholm wrote:

> > OK. One or two refs?

> >

> > Can you simply try to edit one of them (or the

> only) one away> from the build options? It guess that the compiler

> adds options> dynamicaly and it might also be different from

> version to version.> It was not clear if the build options was

> specificaly setup> for the current version of the

> compiler...>

> > Jan-Erik.

> Thanks for your thoughts, but I managed to find an installer .exe which

> has bought me some 45 days of evaluation time, while I try to find the=20

> original purchased license key. The compiler now compiles the legacy=20

> code without a fight! The next problem looks like getting a debug header

> for this 16f616 in question, or migrating to a part that debugs=20

> in-circuit with the ICD3.

>=20

> Regards

> Matt

> --=20

>=20

> http://www.piclist.com/techref/piclist PIC/SX

> FAQ & list archiveView/change your membership options at

> http://mailman.mit.edu/mailman/listinfo/piclist

>=20

>=20




--=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
.