Strange failure

[vodka]

Hello , i have a problem with a pic18f4520 when i use with the programmer TL866A .

The trouble begin when i try to read the ic . the software get out this  error message "ID error, Checked ID is 0x000 ".

And then i take off the option "Check ID device" ,i return to read the ic. At the hex dump viewer show me the rows and columns full from zeros   .
The next step that i do ,it is a ic test with the option "Blank check"  and show me a info message that the flash memory isn't empty and this mark all the positions that it has different values ,
when before the ic seemed that it didn't read.
Furthermore, sometimes the " id code IC "acknowledge me and it works without problem .

Is it possible that the ic suffered a electrostatic shock when i manipulated with the nude hands? And if so why isn't the IC dead ?

[ElektroQuark]

There is no good contact between pins and socket or the IC is in an incorrect position.

[vodka]

i just to clean with isopropyl alcohol the ic pins and i return to fail but this time the id code device is 0x7f7.

[ElektroQuark]

The ZIF socket is very bad. Try realocating the IC some times and test.

[vodka]

The ZIF have been tested with other ic(eeprom ,flash) and with other pic18f4520 that i have in the reserve.

[vodka]

I returned to prove and it follows show me the id code 0x7F7, i take off the option "Check device" and it shows me in the  hex dump viewer   the rows and columns full from "0xFE"
Does the ic mock me ? it says me that i have faith.

Do Somebody know as work the internal programmer system of the IC MICROCHIP?
I have hunch that the strange work is provoked for the system identification of the ic

[Chris C]

Converting to binary, and aligning the bits a bit differently:
11111110111 (0x7F7)
11111110 (0x0FE)

Notice you're getting the same, repeating bit pattern regardless of whether it's accessing the Device ID or the FLASH.

I have seen this exact symptom whenever there is a bad connection between the programmer and the chip.  Examine the pins on the troublesome PIC, and see if they're bent at a different angle from the PIC that works.  If so, maybe your ZIF socket is just loose enough to fail only with that particular PIC, and it could be corrected by carefully bending the PIC pins.

But if that doesn't help, and considering that your other chips work, you might really have a damaged PIC.

[vodka]

EdoNork and Chris C have reason , the problem were a bad connection between the IC and the ZIF. i have done a few proves, moving the IC for the socket until i achieved that read id code .
The solution is very simple , only there are that tighten with a few force the ic versus ZIF and go down the toggle for blocking

Thanks

[Chris C]

Glad you were able to solve it!