PIC KIt 3 programming Error

[SANEMB]

While flashing the code in pic18f27j13 controller.we are getting the below programming error using PICKIT 3 as well as MPLAB ICD 3 programmer. Please find the attached snapshot.

Target Device ID (00000000) does not match Expected Device ID(00005690).

Please advice.

[gan_canny]

Read the data sheet for the PIC twice.. especially the programming section
Check MCLR has a pull up ( 10k works)
Check PGC PGD .....now if they aren't on the standard pins (ex RB7 RB6) make sure your fuse points to the pair you have wired.
Check ground and Vcc

[Amon]

And power your board.

[metal]

and update your MPLAB copy.

[motox]

That’s an electrical problem. Check all connections, power supply and keep the cable between the programmer and the device shorter than 15cm. I had soooo many programming issues because the cable was too long.

[Skarden]

I had the same problem and it was caused by the printer driver (Samsung cpl-310) in my case.
Stopping the application running in the taskbar (the one that gives the ink level status) fixed the problem.
Regards

[piappo]

The pic is bad or the problem is in the two line pgc pgd.

[Skarden]

Hello,
I have another (strange) message like that :

"Target Device ID (0x0) does not match Expected Device ID (0x0)"

This happens since I installed MPLABX 1.6 trying to program a 16F1455 with a pickit 3.

Trying to program a pic32, this doesn't happens.

The (strange) think is that, if I ignore this message, the pic is programmed properly even in debug mode!

So I think it's a bug of the 1.6 version (maybe in the firmware uploaded in the pickit 3).

Wait for next release ? .....

[xpress_embedo]

Are you using a Genuine PIC Kit 3 from Microchip or some clone as i read somewhere you are suggesting someone to use PIC KIT 3 Clone from ebay.

May be it is the Problem of that clone.
Try to program some other controller on some other board, to check whether your PIC KIT 3 is okay or not.

I get this error few days back, and my case the controller was faulty, i don't know how 

Also check your connections and power supply voltage.

[Skarden]

Hello,
my programmer is a clone bought on ebay but it's build on the original schematics and use the original software.
The bug relates just to the error message as, if I ignore it, the programming and the debug works properly.
The snag I found concerns only the 16F1455 as it works without any problem with other kinds of PICs.

I tried to roll back to MPLAB-X 1.51 and I confirm that the problem disappear.

[juvann]

I will receive PIC16F1455 in a few days, I have an original PicKit3 so I will try it. You can try to open a case in Microchip's support.
Have you tested also with Mplab IPE?

[Skarden]

Yes, same problem.

[juvann]

Microchip tell me, they will resolve the issue in the next release of MPLabX

[Skarden]

Same problem for the 16F1459 too !

[thunderer]

Those chips are younger than Pickit3 (and even Pickit2) so some hiccups are normal. They said both Pickit 2 and 3 will have a fix for these chips. Go to Michochip forums for more details. Then get back here once solved to let us know 

[pheonixtech]

I'm not too familiar with the 18F series, but it may be worth checking your config bits to make sure that you have the correct ICSP port selected on the micro. I know with the 24FJ64GA002 et al that you have 2 or 3 sets of PGD and PGC pins. I've had a headache before with this...

Posted on: December 29, 2015, 12:19:59 00:19 - Automerged

[BharatSujanani]

I had same problem with MPLAB IDE.
Than i have tried this in MPLAB x IDE than there is no problem.
PLease try this.

[sakugava]

Did you try the Pickit3 software? Download: https://drive.google.com/open?id=0B53UZBCi_9pFXzc0ekxlWGFFMVE

[hanle]

You can use function "Download PICkit Operating System" from Tool menu. It maybe resolve this problem.

[hunter07]

Clean your PCB with isopropyl alcohol then pressured air. There may be some short circuit or low resistance between pads/tracks due to solder paste residue.
Good luck

[GroundPlaneLoop]

Check comm on PGC/PGD and MCLR level w scope. Seems to be a problem related with connection. Also try to reflash the bootloader in the Pickit - holding the button and connecting USB, then download OS with the pickit3 app.
The pickit3 standalone app is somewhat buggy, and regarding clones, I have also a clone and sometimes the OS upgrade is stuck, but with the button trick, it is possible to recovery it. Have some problems with uploading OS from MPLAB also, but only use it for programming.

[natur3k]

I came across a similar problem with PIC18 and original PICKIT3.
At first we suspected a HW issue but many more brand new MCUs were tested with the same result.

I checked and excluded other problems first i.e. configuration, MCU to PICKIT3 connection, software.

Environment:
MPLAB X IDE v4.05 @ Windows 7 x64

Solution that worked for me:
I tried the older firmware from MPLAB IDE v8.92, i.e. PK3FW_012890.jam (2013-06-13), from Microchip archives.
In your project go to Options, 'Firmware' category, uncheck 'Use Latest Firmware' and choose the older firmware.

[PM3295]

I found, for some reason, when I use MPLAB IDE v8.84, I get the same ID problem, but only on a Win 7-64 machine. On a 32 bit machine, it works without a problem.

[towlerg]

Given the previous post this clearly isn't the problem but for anyone reading this thread at a later date. On another board it was pointed out the with PGD and PGC TISE'ed as outputs, MCLR disabled and some combination of fuses it was necessay to use the "Use Vpp first program entry" option (available on both Pickit2 and 3 GUI and IPE).

[natur3k]

Given the previous post this clearly isn't the problem but for anyone reading this thread at a later date. On another board it was pointed out the with PGD and PGC TISE'ed as outputs, MCLR disabled and some combination of fuses it was necessay to use the "Use Vpp first program entry" option (available on both Pickit2 and 3 GUI and IPE).

Well, my solution was an answer to a rather different question, i.e. 'my PICKIT3 is properly attached to target MCU, I followed the documentation and googled a lot, but still the device ID cannot be found', and flashing brand new MCUs.

Just now I checked Microchip forums, where 8.92 version was mentioned as a working one (however, older than 8.92 versions were disadvised). PICKIT3 reflashing is not such a problem, really.

[flyback]

I got the same problem with Pickit3: Target Device ID (00000000) does not match Expected Device ID...
Pickit2 do not have this behavour.

I follow the recommendation in
http://www.microchip.com/forums/m753427.aspx

download
http://ww1.microchip.com/downloads/en/DeviceDoc/PICkit3%20Programmer%20Application%20v3.10.zip

Run it using admin right to download new firmware & change to MPLAB mode (tools->revert to MPLAB mode)

it works now, device IC is finally recognized. I use MPLab 8.92, on Windows 10 32bit (vers 1804)

Good luck.



Posted on: May 16, 2018, 02:22:05 02:22 - Automerged
PS: I remembered now: I just did "tools->revert to MPLAB mode".
then back in MPLAB 8.92. The MPLAB now downloaded the corresponding firmware.

[Poty]

As a few fellows said, the problem is usually a faulty connection. Double check eeach one, and verify wheter the circuit is connected to an external power source or to the Pickit 3 source. Keep in mindo that Pickit 3 power source is limited, and if your circuit needs more power than it has, you`ll have to connect it to an external source. In that  case, select "no power from pickit 3 (or so...)" from the mplab menu, and obviously, verify that pickit 3 is perfectly protected. After that, remember that pickit needs some software depending on the pic family that you´re programming, so, let it get that from internet, it does this automatically. And after all that, if you keep getting this error, start to thonk that you probably blowed up your pic. But double check all once again, just to be sure.

As an example, once I was becoming crazy with this error, and the problem was the way the pickit was connected to a test board. It uses a 6 wires RJ11, and the socket on the test board was loose, and made bad contact. So, you can find bad contacts almost in every part, so you must become paranoid..   

Just kidding, but a nice check is allways good.

Regards,