• AVR Freaks

AnsweredHot!"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION!

Author
dreeke
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2011/04/28 07:43:51
  • Location: 0
  • Status: offline
2012/08/28 05:02:39 (permalink)
0

"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION!

Hi all,
 
I had to pick up an older project which was made with the help of a Microchip FAE so there are absolutely NO hardware issues nor software issues.
I reopened my old project which has always worked and tried to program my old board. Guess what, again I get this annoying message! Swapping boards, ICD3's, rebooting the pc DOES NOT HELP!
 
The cause is some debug session which was wrongly (?) closed leaves traces in the ICD3. By trying to put it back in debug mode suddenly reactivated the ICD3. After leaving the debug mode in a normal way (that is: without having it crash....) programming worked again.
 
I hope this will give a hint to the engineers of Microchip to finally get rid of some REALLY annoying crashing of the tools.
 
 
#1
Alltair
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2011/11/01 04:35:16
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2012/08/30 07:45:12 (permalink)
0
Just thought I'd report this
I've been having loads of trouble with
Target Device ID (00000000) does not match
expected Device ID (00002020)
on what was a working system The Oscillator crystal stopped working when the problem presented.
I built a second test board with no change and tried several PC's running MPlab
finally I did a clean install of MPlab on a new machine.
after the installation (here is the good bit) It asked if I wanted to upgrade the IDC3 firmwear
and after that all was fine.  I no longer get the message  target etc.  just the target Device ID revision, and the oscillator is running
 
I have yet to see if programming a target causes a recurrence of the problem but this cost me 2 days of faffing about
 
Perhaps with this hint we can have a comment from Microchip about what is going on
#2
profiler1234
New Member
  • Total Posts : 7
  • Reward points : 0
  • Joined: 2013/01/19 08:36:03
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2013/01/20 05:28:46 (permalink)
0
Hi all,
 
This is the most annoying message:
<Target Device ID (00000000) does not match expected Device ID (xxxxxxxx)>
<Target Device ID (0x0) does not match expected Device ID (xxxxxxxx)>
and
<If you experience persistent problems communicating, the ICD 3 test interface can be used to help diagnose the problem>

"Device ID (00000000) or (0x0) "  means:    no contact at all.
But then we know that before this message appeared, everything worked fine. So if ICSP pinout & cable connection is OK,
and if it applies, checking PGCx and PGDx settings in config and if that is OK,
what is the real reason.
Other then the result being some corrupted setting in the ICD3.
The ICD3 should have its own reset en reboot button !

My way of doing this is rebooting and updating ICD3 by plugging it in a different PC with MPLAB or MPLAPX.
 
 
 
#3
VulcanLLC
Starting Member
  • Total Posts : 19
  • Reward points : 0
  • Joined: 2013/08/29 17:28:29
  • Location: Arizona USA
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/06/17 13:08:04 (permalink)
0
I concur with the original poster - after switching the driver for ICD3 to MPLAB, the ICD3 could not read the device ID.  Switching from programmer to debugger, then back to programmer from within MPLAB enabled the ICD3 to read the device ID and consequently program the device.  I also threw in a couple of reboots which may or may not have been necessary.
 
- Mike
 
#4
gaubuali
Starting Member
  • Total Posts : 27
  • Reward points : 0
  • Joined: 2008/10/18 09:34:27
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/01 02:23:46 (permalink)
0
Hi,
 
If you thing that your target board is powered up correctly, in this case, the MCLR line may cause problem. 
I can isolate everything that concerns about the MCLR line then try again.
 
Hope this can help. 
 
Regards.
#5
Chris Jordan
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2014/08/01 06:44:24
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/01 07:57:50 (permalink)
0
We have had this problem intermittently on a project using a PIC16F886.  We use both ICD3 and Pickit3 programmers driven from MPLAB8.
The problem turned out to be that the RB3/PGM pin (which drives the anode of a led on our board), was floating high during programming, this was causing the PIC to try and enter low voltage programming mode while our programmers were trying to use high voltage mode.
A simple cure was to put a 10K resistor across the led to provide a ground path.
So, if your PIC has a PGM pin (Usually RB3 or RB5) check that it cannot float high during programming!
Hope this is of some help.
 
Regards to all...
 
#6
DarioG
Allmächtig.
  • Total Posts : 54081
  • Reward points : 0
  • Joined: 2006/02/25 08:58:22
  • Location: Oesterreich
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/01 14:40:56 (permalink)
0
Yeah, or disable it in the CONFIG words Smile

GENOVA :D :D ! GODO
#7
ric
Super Member
  • Total Posts : 23598
  • Reward points : 0
  • Joined: 2003/11/07 12:41:26
  • Location: Australia, Melbourne
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/01 16:20:20 (permalink)
0
DarioG
Yeah, or disable it in the CONFIG words :)


Doesn't help for the very first time you program the board. ;)

I also post at: PicForum
Links to useful PIC information: http://picforum.ric323.co...opic.php?f=59&t=15
NEW USERS: Posting images, links and code - workaround for restrictions.
To get a useful answer, always state which PIC you are using!
#8
DarioG
Allmächtig.
  • Total Posts : 54081
  • Reward points : 0
  • Joined: 2006/02/25 08:58:22
  • Location: Oesterreich
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/02 02:01:57 (permalink)
0
ric
DarioG
Yeah, or disable it in the CONFIG words :)


Doesn't help for the very first time you program the board. ;)




 
Hmmm yeah I considered that even yesterday while posting the above :) but, as far as I can remember, I never had issues "even the first time" and even if I usually did not care about what was connected to LVP pin (whichever on several PICs). So, was I just lucky?
Actually the "problems" arising from LVP are at run-time, not at high-voltage programming time..?

GENOVA :D :D ! GODO
#9
Ian.M
Super Member
  • Total Posts : 13225
  • Reward points : 0
  • Joined: 2009/07/23 07:02:40
  • Location: UK
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/02 02:47:28 (permalink)
+2 (2)
Some of the early PICs with LVP had a flawed implementation and glitches on the PGM pin could interfere with HVP corrupting the programmed image.   Its a similar issue to the old PIC16C84 programming problem where transitions on OSC1 while /MCLR was rising from the RESET threshold to the VPP threshold incremented the program counter which was also used as the address pointer during programming, offsetting the image by an arbitrary number of words.  However I don't think anyone has done a detailed analysis of what is actually going wrong or even made a comprehensive list of affected chips.
 
As a bulk erase resets the whole CONFIG to defaults, and LVP is on by default and after a bulk erase the programming algorithm requires that programming mode is exited then reentered to leave the configuration memory space  reset the address pointer to the beginning of the program memory space, there is a short interval where glitches on PGM can cause problems. Hence the common practice to always have a pulldown on PGM during programming.

--
NEW USERS: Posting images, links and code - workaround for restrictions.
I also support http://picforum.ric323.com because this forum is sometimes too broken to use!
#10
DarioG
Allmächtig.
  • Total Posts : 54081
  • Reward points : 0
  • Joined: 2006/02/25 08:58:22
  • Location: Oesterreich
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/02 03:14:36 (permalink)
0
I see Ian, thanks !

GENOVA :D :D ! GODO
#11
Chris Jordan
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2014/08/01 06:44:24
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2014/08/13 02:23:10 (permalink)
0
Thanks Ian, that's exactly what I thought was going on.  I'm not sure how long the 16F886 has been around, but it certainly suffers from this problem.
Cheers all... Chris
 
#12
KR1
Senior Member
  • Total Posts : 123
  • Reward points : 0
  • Joined: 2015/05/11 17:26:44
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2015/06/25 22:02:53 (permalink)
+2 (2)
Sometimes this error is caused by simply not paying attention Smile: Smile 
for example I usually use PICs but sometimes I ve used pre-built boards with PICs inside whose pins are almost a reflection of the pins of its PIC, so they are programmed in the same way as a PIC.
 
But... (there is always a but), for some reason these boards, small as they are makes my eyes mistake the connections. For example the connection from the programmer to MCLR is actually connected to the hole next to it, or the ones in PGD.. it is just that I misconnect the cables.
 
In a few words Target Device ID (0x0) means there is something you are not connecting well, so first check the connections.
#13
NorthGuy
Super Member
  • Total Posts : 5590
  • Reward points : 0
  • Joined: 2014/02/23 14:23:23
  • Location: Northern Canada
  • Status: online
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2015/06/26 06:08:16 (permalink)
0
KR1
For example the connection from the programmer to MCLR is actually connected to the hole next to it, or the ones in PGD.. it is just that I misconnect the cables.


Happens all the time to me. And it's getting worse with years ... I now check all connections with a big
magnifting glass before turning on the power.
#14
scrungy
Senior Member
  • Total Posts : 134
  • Reward points : 0
  • Joined: 2016/02/02 09:56:54
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2016/06/16 18:38:02 (permalink)
0
In am having similar issues.  For a while the ICD3 was not responding to anything.
I have seen this a time or two, and don't know how to fix it.  I think the last time I fixed it was just by unpluging it for 30 mins or so...  But right now I need it working and it isn't
 
#15
iqram
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2019/06/16 10:21:47
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2019/06/21 23:14:30 (permalink)
0
The dsPIC30F flash programming specification suggests to have VIHH voltage on MCLR while entering into ICSP mode. This is 9V to 13V. I scoped the MCLR pin while connecting MPLAB X IPE with my target board and it is going maximum 5V. I am suspecting that is the reason I am unable to detect dsPIC30F4011 using Pickit 3 plus MPLAB X IPE.
 
Is there any way to set MCLR to high voltage while ICSP? I tried looking into MPLAB X IPE settings but it is not allowing me to set MCLR to high voltage.
 
Please suggest.
 
Thanks.!
Iqram
#16
iqram
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2019/06/16 10:21:47
  • Location: 0
  • Status: offline
Re:"Target Device ID (0x0) does not match expected Device ID" - THE REAL SOLUTION! 2019/06/22 00:32:57 (permalink) ☼ Best Answerby GeorgePauley 2019/06/24 14:53:32
0
The problem is solved. It was MCLR voltage issue only. I downloaded latest version of MPLAB X IDE (v5.2) and used MPLAB X IPE. The MCLR is going till 12V and dsPIC30F4011 is detected with two different Pickit 3 programmers.
 
The previous version of MPLAB X IDE was 2.0.
 
Thanks.!
Iqram
#17
Jump to:
© 2019 APG vNext Commercial Version 4.5