PICList: 1, Microchip tech support: 0 Can you believe that answer from Microchip support? Did that totally miss the point or what? I have never tried to ask them a question, but I have to wonder if they are often this far off. Anybody want to start a "Microchip support people say the darndest things" page? Are there other good examples of clueless responses from support? If this is the average response, they should just fire the support staff, forward tech.support@microchip.com to piclist@mitvma.mit.edu and pay PICList members for support answers. --- James Newton (PICList Admin #3) mailto:jamesnewton@piclist.com 1-619-652-0593 PIC/PICList FAQ: http://www.piclist.com or .org -----Original Message----- From: Tech.Support@Microchip.com To: "William K. Borsum" Subject: Re: Picstart Plus and Code Protect issues X-Mailer: Lotus Notes Release 5.0.2a November 23, 1999 Sender: tech.support@Microchip.com Date: Tue, 19 Jun 2001 15:04:01 -0700 X-MIMETrack: Serialize by Router on USMail1/US/Microchip(Release 5.0.5 |September 22, 2000) at 06/19/2001 03:04:03 PM, Serialize complete at 06/19/2001 03:04:03 PM Kelly, Once the code protection bit is set in a (OTP) one time programmable device, you cannot change it. In addition, if you have a window part, you can change its program by erasing the device. However, if a window device is code protected, you cannot uncode protect the device with UV light. Therefore, we do not recommend code protecting windowed parts. Regards, Benjamin Giguere Engineering Support **************************************************************************** ** Web Site: www.microchip.com **************************************************************************** ** "William K. Borsum" 06/18/2001 12:26 PM To: cc: Subject: Picstart Plus and Code Protect issues Hello: Just ran into a problem where we programmed a series of 16C57's and '54's with the code protect bit ON. Turns out we had a faulty adapter socket and some and/or all of the chips were trashed. Question: In the new versions of MPLAB, it appears that there is no way to program the chip with code protect off, verify, then set code protect to ON. I would like to know if there is any way to do this at all? Is it possible to program the device twice? Once with code protect off, then a second time with it on? Or is there some way to tell MPLAB to just turn on the code protect bit? Thanks Kelly -----Original Message----- From: pic microcontroller discussion list [mailto:PICLIST@MITVMA.MIT.EDU]On Behalf Of Roman Black Sent: Monday, June 18, 2001 10:04 To: PICLIST@MITVMA.MIT.EDU Subject: Re: [PIC]: Program, verify, then code protect 16C54/57 with picstart+ Importance: Low James Newton. Admin 3 wrote: > > I'm forwarding this to the list for William K. Borsum.... > > "I want to be able to program a chip (16C54C and 16C57 to be precise) with > code protect off, verify the program was burned correctly, then set the code > protect. MPLAB and the PicstartPlus do not appear to support this. Does > anyone know how to do this? Can the chips be programmed twice (same code), > but once with the code protect off, then verify, then program again with > code protect on?" I use MPLAB and PicStart Plus, yes it does support this. First the code is programmed, then a verify is done, then the code protect is set last. (otherwise it couldn't verify!) This is automatic, if you watch the yellow light on the PSP you can see it flicker after programming when it starts the verify. If it fails the verify it leaves the code protect off so you can see what went wrong. -Roman -- http://www.piclist.com hint: The PICList is archived three different ways. See http://www.piclist.com/#archives for details. -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listserv@mitvma.mit.edu with SET PICList DIGEST in the body