On Mon, Feb 28, 2011 at 9:11 PM, Dave Tweed wrote: > Manu Abraham wrote: >> Today, I changed connectors again, but got identical behaviour. >> >> verify nevertheless fails. Device doesn't seem to be programmed >> correctly either. >> The logs look thus: >> >> Connecting to MPLAB ICD 2 >> ...Connected >> Setting Vdd source to MPLAB ICD 2 >> Target Device PIC18F452 found, revision =3D c0 >> ...Reading ICD Product ID >> Running ICD Self Test >> ...Passed >> MPLAB ICD 2 ready for next operation >> Erasing Target Device... >> ...Erase Succeeded >> MPLAB ICD 2 ready for next operation >> Blank Checking... >> ...Program Memory >> .. Config Memory >> ...EEPROM >> ...User ID Memory >> ...Blank Check Passed >> MPLAB ICD 2 ready for next operation >> Verifying... >> ...Program Memory >> ICD0161: Verify failed (MemType =3D Program, Address =3D 0x0, Expected V= al >> =3D 0xEF33, Val Read =3D 0xFFFF) >> MPLAB ICD 2 ready for next operation >> >> If the issue is with the cables, the device type and version detection >> should also fail, right ? > > Am I missing something here? According to the log, you erased the device, > confirmed that it was blank, and then tried to verify, which failed. Ther= e > doesn't appear to be any attempt to program the device at all. uhmm, true .. That was quite dumb of me that I didn't think that verify would be comparing against the flash image. Right now, programming appears to work fine again. I will post again when verify fails after a successful Program again. Thanks, Manu --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .