Hi,

On Sat, Feb 26, 2011 at 6:16 PM, PicList <piclist@sentry.org> wrote:
> Manu Abraham wrote:
>
>> - get verify failed after a device Program, device verify
>
> [...]
>
>> I thought it could be the cables, connectors... but that seems quite
>> unlikely as I have tried replacing them, still see this issue in some
>> cyclic manner.
>>
>> Anybody else seeing such a weird behaviour ?
>
>
> Identical symptoms with a PICkit2 - it was the cable - several in fact.
> Expensive "thick" cables caused the problem. Cheap "thin" cables worked
> fine.


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 Val
=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 ?

Best Regards,
Manu
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.