That's EXACTLY correct BAJ, trust the write.  If you can't read it back,
neither can anybody else.  And that's a good thing.  A write went bad?  What
are the odds of that?  Slim.  So?  Just flash it again.  No problem.

-----Original Message-----
From: pic microcontroller discussion list
[mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Byron A Jeff
Sent: Thursday, July 26, 2001 9:03 AM
To: PICLIST@MITVMA.MIT.EDU
Subject: Re: [PIC]: FINAL WORD: A great solution for the PIC16F877
problems (code protect,bootloader)


On Thu, Jul 26, 2001 at 08:12:15AM -0400, M. Adam Davis wrote:
> Ideally the code protect (including the ICSP disable) would occur AFTER
> the verify.

This is not possible. When programming the chip with internal writes, the
config word is inaccessible. You can't change any of the config bits. That
can only be done when programmed externally.

What Ron proposes is a black hole. You have to trust that the write works
correctly.

BAJ

>
> -Adam
>
> wouter van ooijen & floortje hanneman wrote:
>
> >>>Very simple:  Allow me to disable ICSP reads no matter what, and allow
me
> >>>
> >>to
> >>
> >>>disable internal reads of the flash memory, but allow internal flash to
> >>>
> >be
> >
> >>>re-written.
> >>>
> >
> >Bad idea, how would you VERIFY?
> >
> >Wouter
> >
> >--
> >http://www.piclist.com hint: PICList Posts must start with ONE topic:
> >[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
> >
> >
> >
> >
> >
>
> --
> http://www.piclist.com hint: PICList Posts must start with ONE topic:
> [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads
>

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads