How to debug with MPLAB and PicKit3 with PicBasic Pro 3 - debugging

[dhouston]

Know your PICs,...Not the other way around

Can't I do both?

My project uses multiple PICs (12-13 if fully populated), most of which will be 12F1840 & 16F1825 or their enfeebled PicAxe variants 08M2 & 14M2. All will be socketed PDIP chips.

The PICs will have the ds30 loader preprogrammed and the PicAxes will have the PicAxe interpreter/loader. Rather than try to make it possible to download to each in situ (too complicated for my ancient grey cells), I am designing a small PCB with a DIP-14 socket that can be used to download programs and, since I doubt this will generate sufficient volume to justify having Microchip burn the ds30 loader into the PICs at purchase, it will also allow doing this with a PICkit 3 programmer.

I'm confused about two things (actually, I confused about many things but let's take them one-by-one). Fig 2.6 of the PICkit 3 User’s Guide shows a resistor between Vdd & Vpp but gives no value. And Fig 28.1 of both PIC datasheets shows a regulator added to the Vpp line from the MPLAB ICD 2, Does this also apply to the PICkit 3? If not, what value resistor, if any, is needed between Vdd & Vpp?

I will not be doing any debugging but it seems related to this thread.

[Joeygo]

in mplab help under pickit3 or icd3 there is a schematic showing the resistor is somewhere between 4k7 and 10k.

The resistor pulls up the Vpp (/MCLR) to Vdd when noting is connected.. during programming the pickit3 or icd3 will driver Vpp low at some stage to put the part in to reset and eventually drive to Vpp programming voltage.



regards
Joe

[dhouston]

in mplab help under pickit3 or icd3 there is a schematic showing the resistor is somewhere between 4k7 and 10k.

Thanks, Joe.