That works fine. I have customers who use this technique for their production. You have to have a burner which allows you to overwrite, rather than forcing a start with a blank chip. Andy Dan Michaels on 04/06/2000 10:58:01 AM Please respond to pic microcontroller discussion list To: PICLIST@MITVMA.MIT.EDU cc: (bcc: Andrew Kunz/TDI_NOTES) Subject: Re: Verifying software rev in production Mike Mansheim wrote: > >I've seen brief "near references" to this topic lately, but haven't seen my >question directly addressed. >We have in production a design that takes advantage of ICSP by programming >the pic (C73B) at the final assembly of the product (using a Promate II). >Several models use the same circuit board, but different software versions. >If code protection is used, what is the best way for our assembly line to >verify the software version that a given board was programmed with? We >would like the ability to check AFTER programming in addition to the usual >check at the time of programming. >It would seem to me that if you cannot read a code protected part, then you >can't do a checksum on it either. Anyone have the scoop on this? >Thanks. > Related to this, is it not possible to program a PIC without setting the code protection, then verify the chip, and then set the code protection afterwards? Or will the CP bits not comply here?