----- From: "Micro Eng" In addition, using the ICD to program the chip in circuit, it seems = that I > don't always get a good burn. In other words, I can program it once, = and > something doesn't work quite right, and then I can reburn, and it does = work. > Anyone else seeing this as well? Back in the days of EPROM programming the specs said 50ms max burn per = byte. Many EPROM programmers used the full 50ms/byte figure which resulted in = the EPROM getting a bit hot. And the programming time could run = something close to 15 minutes for a 16k(byte) device, which seemed like = forever. Then along comes a new "fast" burner that could do the job in a = matter of seconds, seemed like a big improvement until you started = having bits fail a day or more after you had got a good verify. Looking = back over the EPROM spec sheets I noticed it said burning 5 times the = minimum required to program (up to a max of 50ms in one session) would = insure the device stayed programmed. New procedure, program at max speed = and if verify failed program again, then multiply the number of = programming cycles it took to put the data in times 4 and burn that many = times more. Shortly after this new software was released that programmed = each byte for 1ms bursts, then read it back, kept looping for a max of = 10 shots then burned it for 4 times that. My suggestion is to program 5 times in a row to insure data integrity = (while monitoring the temp with a finger to protect against cooking the = device), until they come up with a patch for the programming software. $.02 Lonnie - KF4HAZ - -- http://www.piclist.com hint: To leave the PICList mailto:piclist-unsubscribe-request@mitvma.mit.edu