Sonsivri

I am trying to Change Device ID of PIC16F676 so that PICKit2 can able to Identify device. Can any one help me

Thanks in advance

regards

ALLPIC

the pickit2 should be able to show you have 16F676 connected by default.
have you tried to reinstalling the pickit2 and mplab software.
or you can select device by manual selection.

actually my bos is asking, if any one try to read IC through PICkit2 or any programer, the componant number should not shown by programer. means I should able to erase deive ID of microchip. If I am not wrong

regards

sorry I just looked the programing specs for the pic16F6xxx.

4.1 Device ID Word
The device ID word for the PIC12F6XX/16F6XX is
located at 2006h. This location cannot be erased.
so only option for you is, to use code & data protection.  
 (unless there is a way to edit location 2006h in the hex file)

Maybe you can erase or change the device ID if you are using Microchip's PM3 programmer..
I believe it can also put in a serial number into the ID location.

or chip may faulty ,partial working ,full working but some ex pins may damage , that may be the case

You cannot change device IDs by design, so I wouldn't waste a lot of time on it, especially for a hundred parts...it's a pretty common procedure to differentiate devices (features, price, yield, speed grade, etc) in the semiconductor industry, even though they all are the SAME CHIP, so they can charge you more when the feature has a VALUE to you (we all share the profit pot is the rule - don't get greedy.....you don't want your chip vendor to go out of business or not provide you with new innovative devices do you?). 

The IDs are usually electrically (sometimes laser link blown) programmed at wafer test, though occasionally it'll be a mask level ROM, right in front of that memory map register location you mentioned

This is to keep unscrupulous companies from buying a cheaper version of the chip and turning on features that weren't meant to be in that ID.  Now you know why pinouts are eerily similar....sometimes it'll be a nonconnected chip pad as well to keep people from hacking to a more expensive, longer test time, chip functionality as well.

Note that you are also risking turning on UNTESTED features if you should ever succeed in hacking the device ID.

I tried in this 2 days but each time I tried I lost a chip. so I think this is enough time I waste on this. And I also personally feel that there is no point to erase device ID if your code is up to mark. :)