Hot damn. Putting that resistor in place did the trick. THANK YOU TO EVERYONE IN THIS THREAD. Here's to hoping I can get some work done before this thing dies on me. On 10/3/06, Xiaofan Chen wrote: > > On 10/3/06, WH Tan wrote: > > > > Think of the header as 2 part. Part A: the extra pins that designed > > for ICD2 communication and setting up some options (like jumper, some > > other type of headers don't have jumper). This part also include the > > ~ICDMCLR, which has taken some reposibility (Vpp) off the usual > > MCLR/Vpp pins as you will find in usual ICD capable device, like the > > high pin count PIC. > > > > PART B: The 8 pins that are mapped to emulate the actual F675. For > > this part to work, you have only one option regarding the > > configuration of the MCLR. It must be configured as MCLR. Not a true > > MCLR as some of its responsibility (Vpp) has been taken by PART A > > (~ICDMCLR), BUT it must still be pull-up to Vdd, as you did with a > > normal PIC's MCLR. Without that the PIC won't run, and the ICD2 > > communication can't be established. Can you just find a 10k resistor > > and connect it to the header to perform the test. It sould be joint > > to pin 3 and pin 6 of the -ICD. You can find the PCB trace and join > > it at the top side of the PCB. Or connect the 10k resistor at your > > target and plug the header in. > > > > I do not think it is a good idea to put the 10k resistor at the top > side of the PCB. It should be in the target board. > > I've used the ICD2 with 12F629 (using the same header as 12F675, > use the jumper setting to disable the ADC inside 12F675). I can > say it is a pain to use. There are many limitations to take note. > It is still usefull but limited. > > >From MPLAB V7.42 ICD2 Help: > PIC12F629/675, PIC16F630/676, PIC16F627A/628A/648A Limitations > PIC12F675-ICD - PIC12F629/675 > > Debugger Limitations: > Device-ICD/ICE Limitations > You cannot single step through an interrupt. > Devices cannot be programmed or read while GP1/RA1 is high (Vih). Move > circuitry that makes GP1/RA1 high to another I/O pin during > development. > Programming these devices while debugging may be slower as these > devices do not have row erase capability. > Programmer Limitations > Program Memory standard flash > > Device-ICD/ICE Limitations > For some devices, only the ICD/ICE version of the device (e.g., > PIC12F629-ICD) can be used to debug with MPLAB ICD 2. > ICD/ICE devices must be used with a header board. See the Header Board > Specification (DS51292). > Only ICD/ICE devices can be programmed using the MPLAB ICD 2 Header. > Use the Universal Programming Module (AC162049) to program regular > devices. > ICD/ICE devices must be clocked (internally on INTOSC or externally on > OSC1) and have MCLR high to communicate with the MPLAB ICD 2. > A breakpoint cannot be set on a GPIO instruction. Since MPLAB ICD 2 > I/O is through bits 6 and 7 of GPIO, setting a breakpoint on a GPIO > instruction will cause communication problems. > > Programmer Limitations > Care should be taken when programming the PLL. > For all devices with EEPROM memory, Erase operations will also erase > EEPROM memory. > If your code makes use of port pins that correspond to Clock and Data > pins in programming mode, you may not be able to reprogram your > device. See Warning 0033 for more information. > > Regards, > Xiaofan > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > -- Shawn Wilton (b9 Systems) http://b9Systems.com <- New web page -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist