> I'm stumped. I've never had this error before unless the clock was
> broken (it isn't).
>
> The PIC (PIC16LF88) runs perfectly at 3.5V, will program my
> "wink" test fragment from the ICD2 as a programmer, and when
> selected as debugger, all seems OK except for the error. (NO, I
> don't have ICD2 selected at both programmer and debugger).
>
> Neither PGC, MCLR, or PGD is connected to anything except the
> debugger. Well, MCLR has a 47K pullup on it only to VDD.
>
> I haven't tried to run the PIC at 5V because it has some 3.6V max
> peripherals attached.
>
> The PIC runs flawlessly for the wink test.
>
> Any ideas, fellow PIClisters?
>
> --Bob
>
> --
> Note: Attachments must be sent to
> attachKILLspamengineer.cotse.net, and
> MAY delay replies to this message.
>        520-219-2363
>
>
>
>
> --
> Note: Attachments must be sent to
>  .....attachKILLspam.....engineer.cotse.net, and
>  MAY delay replies to this message.
>         520-219-2363
>
> _______________________________________________
> http://www.piclist.com
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>

>>The PIC (PIC16LF88) runs perfectly at 3.5V, will program my
>>"wink" test fragment from the ICD2 as a programmer, and when
>>selected as debugger, all seems OK except for the error. (NO, I
>>don't have ICD2 selected as both programmer and debugger).
>>
>>Neither PGC, MCLR, or PGD is connected to anything except the
>>debugger. Well, MCLR has a 47K pullup on it only to VDD.
>>    
>>
>
>FWIW, we currently have the same problem here (same chip, same setup, same
>symptoms)... no solution yet.
>
>Gerhard
>_______________________________________________
>http://www.piclist.com
>View/change your membership options at
>http://mailman.mit.edu/mailman/listinfo/piclist
>
>
>  
>

>Bob Axtell wrote:
>
>  
>
>>BUT - if the ICD 2 doesn't work at 3.5V, I have a serious problem, as
>>everything in MY foreseeable future is 3.5V.
>>    
>>
>
>Hi Bob,
>
>If you ever code protect the PIC16F87/PIC16F88 and then want to reverse the
>code protection bits in the future, the *only* way to do such is through a
>chip erase, and Vdd must be in the range of 4.5 volts to 5.5 volts to
>initiate a chip erase. This means that your board has to be designed to
>handle the application of this higher Vdd to accomplish this (without
>adversely affecting your 3.5 volt devices in the process).
>
>A lot of flash PICs at the moment have this constraint. Take a look at the
>programming specifications for more details.
>
>Best regards,
>
>Ken Pergola
>
>
>_______________________________________________
>http://www.piclist.com
>View/change your membership options at
>http://mailman.mit.edu/mailman/listinfo/piclist
>
>
>  
>

>AFAIK, MPLAB overrides the debug bit.
>
>  
>
>>Also, you are having a problem with the Microchip ICD 2, and not on the ICD
>>2 clone, correct? Or are you seeing this problem with the ICD 2 clone as
>>well?
>>    
>>
>
>We are using a clone. And that same clone is working fine on another board
>with an 18F458 (5V).
>
>  
>

>Gerhard
>_______________________________________________
>http://www.piclist.com
>View/change your membership options at
>http://mailman.mit.edu/mailman/listinfo/piclist
>
>
>  
>

> I get that error if I have code protect set on any
> flash or if I have
> table write disabled on any flash or the config bits
> (I'm used to working
> with the PIC18F series).
>
> Good luck!
>
> Harold
>
>
> > I'm stumped. I've never had this error before
> unless the clock was
> > broken (it isn't).
> >
> > The PIC (PIC16LF88) runs perfectly at 3.5V, will
> program my
> > "wink" test fragment from the ICD2 as a
> programmer, and when
> > selected as debugger, all seems OK except for the
> error. (NO, I
> > don't have ICD2 selected at both programmer and
> debugger).
> >
> > Neither PGC, MCLR, or PGD is connected to anything
> except the
> > debugger. Well, MCLR has a 47K pullup on it only
> to VDD.
> >
> > I haven't tried to run the PIC at 5V because it
> has some 3.6V max
> > peripherals attached.
> >
> > The PIC runs flawlessly for the wink test.
> >
> > Any ideas, fellow PIClisters?
> >
> > --Bob
> >
> > --
> > Note: Attachments must be sent to
> > RemoveMEattachTakeThisOuTengineer.cotse.net, and
> > MAY delay replies to this message.
> >        520-219-2363
> >
> >
> >
> >
> > --
> > Note: Attachments must be sent to
> >  spamBeGoneattachspamBeGoneengineer.cotse.net, and
> >  MAY delay replies to this message.
> >         520-219-2363
> >
> > _______________________________________________
> > http://www.piclist.com
> > View/change your membership options at
> > mailman.mit.edu/mailman/listinfo/piclist
> >
>
>
> --
> FCC Rules Online at http://www.hallikainen.com
> _______________________________________________
> http://www.piclist.com
> View/change your membership options at
> mailman.mit.edu/mailman/listinfo/piclist
>