Hi Bruce and Neil,

Don't recall ever setting MCLR in the programming interface, or in the asm
file, but who knows.  If I did, it was accidental within the programming
interface.

The configuration is set as follows:
__config _CP_OFF & _DATA_CP_OFF & _LVP_ON & _BODEN_ON & _MCLRE_OFF &
_PWRTE_ON & _WDT_OFF & _INTRC_OSC_NOCLKOUT

I did manage to salvage one of the chips that were unrecognizeable, using
some combination of checking communication with VPP set, and then erasing it
in normal programming mode.  Not sure exactly what the combination should be
for restoring it to working order, but I still have two that are messed up.
What exactly should I be using to fix this?

I seem to see that others are having this exact problem, which tells me it's
not out of the ordinary.

I hadn't been powering VDD to the target during programming, but maybe the
scenario existed where I accidentally left it on after testing a little
bit.  Ideas?

-Eric

On Sat, Nov 14, 2009 at 2:40 PM, PICdude <picdude3@narwani.org> wrote:

> Sounds vaguely familiar to a problem I had with setting internal MCLR
> and internal osc simultaneouly with a 16F819 some time back.  Could
> your problem be related to this?
>
> Cheers,
> -Neil.
>
>
>
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist