ICD3 Error: Target Device Mismatch - Page 1
Forum section: electronics / general

author: jpanhalt
author_rank: Super Contributor
timestamp: January 18, 2023, 06:50:44 am
content: Chip: PIC16F1789Tool: MPLab 8.92Language: Assembly (MPASM)Error (see attached) In brief, Err0086 Target Device ID 00000000 does not match expected 0000302aThe correct device ID is 00000000. To my knowledge, no real PIC16F device has an ID 0000302aThis problem seems unique to that chip family in my limited experience. The version that is installed currently is a 44 TQFN. I first observed it more than 2 years ago when I switched from a 16F1829 for more pins. Opened a ticket with Microchip (MCC). Nothing satisfactory came of it. Reloaded MPLab 8.92 and problem resolved. Then happened last year. Same story. Opened a ticket with MCC, ran in circles, no constructive help. Reloads didn't help. Internet search revealed others had had same problem and suggested installing an earlier .jam file. After about 2 months MCC sent me a link, and I was able to get an older .jam file which seemed to resolve the problem ... until tonight. Just last week and earlier this evening the chip was reprogrammed without a problem. The older .jam file is still installed.I have gone through the MCC ICD3 troubleshooting guide with no success. Any suggestions aside from constantly deleting and reloading MPLab 8.92 with the older .jam file?

author: woofy
author_rank: Frequent Contributor
timestamp: January 18, 2023, 12:18:43 pm
content: An ID of 00.. . usually means the connections are incorrect or broken. Check you have those correct and that Pdat and Pclk are the right way around. An MCLR pullup of 10k or less has also given problems for me in the past, try 47k to be sure. It could also be just the chip died, try another if you have one. ICD3 is very old. I've not used mine in years, just PICKIT4 now.

author: jpanhalt
author_rank: Super Contributor
timestamp: January 18, 2023, 05:31:52 pm
content: I went through that matter of ID = 00000000 last year. I don't have the manual at hand right now, but as I recall the manual was ambiguous as to whether the ID or ID revision was should not be 00000000. Generally, in the output screen, it does not show a chip ID and only shows the ID revision. At least, I don't recall seeing the actual chip ID in the output screen before.I got it working with my PK3 and here is what it shows for the device ID revision (attachment 1). Note: ID Revision 00000000, which is correct for the chip I have installed.The errata for the 16F1789 shows both device ID, which agrees with the "expected value," and device ID revision (attachment 2). Perhaps, that's the problem. ICD3 is reading device ID revision when it should be reading device ID sometimes. That does not happen with the 16F1829 nor did the PK3 seem to show it. In fact, the errata for the 16F1829 doesn't even show the device ID's. It only shows the revisions (attachment 3). (Actually, it seems to show a 9-bit device ID but doesn't decode it.)

author: djsb
author_rank: Super Contributor
timestamp: January 18, 2023, 06:13:12 pm
content: Have you tried using MPLABX 6.05 instead. ICD3 works with MPLABX. Maybe Microchip did not respond because MPLAB 8.92 is no longer supported?

author: jpanhalt
author_rank: Super Contributor
timestamp: January 18, 2023, 07:21:10 pm
content: MCC responded. But their response was not on topic. Basically, MCC advised me to install current X software and get an ICD4. Does its current software run on a Windows 7 machine? For how much longer?I write Assembly code for fun and challenge to do all sort of not very useful stuff. For example, a few weeks ago I wrote code to do 12-bit BIN2BCD. I thought I might need it for an absolute pressure gauge that was sent to me by mistake. I didn't need it, but it was a good way to pass time and keep me out of trouble.It occupies the Winter when I am not outdoors tending to my hobby farm. Much of the software on my PC will not run with Windows 10 or later. It is simply not worth it to me to change.

author: SiliconWizard
author_rank: Super Contributor
timestamp: January 18, 2023, 07:52:19 pm
content: Quote from: jpanhalt on January 18, 2023, 07:21:10 pmNice!