This chip doesn't read all 0000 or all FFFF.=A0 Regardless, I am pretty cer= tain this one is not erased.=A0 = Randy Abernathy CNC and Industrial Machinery = service, repair, installation and = design 4626 Old Stilesboro Rd NW Acworth, GA 30101 Fax: 770-974-5295 Phone: 678-982-0235 E-mail: = randyabernathy@bellsouth.net --- On Fri, 6/11/10, Isaac Marino Bavaresco w= rote: From: Isaac Marino Bavaresco Subject: Re: [PIC]Copy from unprotected PIC then programming another PIC To: "Microcontroller discussion list - Public." Date: Friday, June 11, 2010, 6:43 PM Em 11/6/2010 19:29, RANDY ABERNATHY escreveu: > I would say chip to chip since I have=A0 been reading the old PIC with my= programmer then inserting another and attempting to burn it.=A0 I know tha= t normally, when a PIC is protected you usually show all FFFF in the memory= and the protected chips I do have show exactly that, however this one does= not, it has different HEX data in each address location which leads me to = think it truly isn't protected.=A0 The person that sent it to me said it wa= sn't.=A0 It is from a rather old controller that operates a heater, fan, et= c. and he couldn't find any of the actual source code left in his files.=A0= Which doesn't surprise me. >=A0=A0=A0 By my experience, PICs read all FFs when erased and all 00s when protected. Make sure you aren't reading an erased chip (or perhaps you erased it by accident while messing around with your programmer). Best regards, Isaac __________________________________________________ Fale com seus amigos=A0 de gra=E7a com o novo Yahoo! Messenger = http://br.messenger.yahoo.com/ = -- = http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist -- = http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist