On 30/03/2011 20:46, Cristiano Cesaretto wrote: > On 30 March 2011 20:16, Olin Lathrop wrote: > >> Cristiano Cesaretto wrote: >>> I can't figure out how the code was deleted from pic. >> You haven't related any symptoms that indicate the code was "deleted". = It >> could be as simple as a single word getting trashed. To start with, I >> would >> read back the data in the PIC with a programmer and compare the result t= o >> the HEX file, or do the verify directly with the programmer if it has th= at >> capability. It might be easier to guess what happened when you know wha= t >> got trashed. >> > When I said deleted I meant "changed", even only in some locations. Changed is a little different from deleted.. It helps to be as accurate as possible when describing problems ;-) > I will try to read the code from the pic and compare with the original he= x, > if I can. the pic is code protected. If it is protected then you will only be able to erase and reprogram, if=20 you try to read it will be all zeros. I would leave the code protect off=20 for now so if it happens again you will be able to read it back and see=20 what's happened. I would not trust the MC code completely either, their=20 code can be pretty bad sometimes. --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .