Does ICD rely on some PIC device's built-in debug ability? (as with ICD2, ICD3 etc.)
Is there a list of PIC devices that can utilize Open Programmers ICD facility. Assuming it's not the same as the list of PIC devices that it can read/write?
What hardware can be omitted if only the ICD function is needed (I already have a PicKit2)?
George.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ICD depends on hardware support; this is present on all PICs, but only described (publicly) for PIC16F devices excluding the newer 16F1xxx.
So this is the support list.
I'm not sure of what you mean with omitted hardware.
There is no interaction with PicKit2.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for responding so quickly. Sorry I didn't explain myself very clearly. The point I was trying to make was that I use a PicKit2 to program PICs and thus do not need Open Programmer for that. I do not use Atmel devices.
I want to use Open Programmer exclusively for its ICD feature. Which I guess means I don't need some of the components for example, the transistors that generate Vpp and VppU.
Your information about 16F's is interesting. Certainly of the ones I looked at 887, 877A and 690 claim on-board debug hardware.
BTW I am aware that I could use the PicKit2 as a debugger but only with MPLAB which I detest.
George
Last edit: Anonymous 2015-03-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You don't need some components for debugging, but you have first to enable it.
ICD debugging requires:
a debug monitor -> you have to use the one developed in this project;
set the ICD flag in the configuration word;
write the debug monitor address in a special location not used for standard programming.
You can probably do the first two with PicKit2, but for the third I have no idea; it is probably done automatically when debugging, I don't know if you can explicitly use that feature.
So the easiest way is to build a full programmer.
Last edit: Alberto Maccioni 2015-03-21
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Does ICD rely on some PIC device's built-in debug ability? (as with ICD2, ICD3 etc.)
Is there a list of PIC devices that can utilize Open Programmers ICD facility. Assuming it's not the same as the list of PIC devices that it can read/write?
What hardware can be omitted if only the ICD function is needed (I already have a PicKit2)?
George.
ICD depends on hardware support; this is present on all PICs, but only described (publicly) for PIC16F devices excluding the newer 16F1xxx.
So this is the support list.
I'm not sure of what you mean with omitted hardware.
There is no interaction with PicKit2.
View and moderate all "Open Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Thanks for responding so quickly. Sorry I didn't explain myself very clearly. The point I was trying to make was that I use a PicKit2 to program PICs and thus do not need Open Programmer for that. I do not use Atmel devices.
I want to use Open Programmer exclusively for its ICD feature. Which I guess means I don't need some of the components for example, the transistors that generate Vpp and VppU.
Your information about 16F's is interesting. Certainly of the ones I looked at 887, 877A and 690 claim on-board debug hardware.
BTW I am aware that I could use the PicKit2 as a debugger but only with MPLAB which I detest.
George
Last edit: Anonymous 2015-03-17
You don't need some components for debugging, but you have first to enable it.
ICD debugging requires:
a debug monitor -> you have to use the one developed in this project;
set the ICD flag in the configuration word;
write the debug monitor address in a special location not used for standard programming.
You can probably do the first two with PicKit2, but for the third I have no idea; it is probably done automatically when debugging, I don't know if you can explicitly use that feature.
So the easiest way is to build a full programmer.
Last edit: Alberto Maccioni 2015-03-21