• AVR Freaks

Hot!MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is correct

Author
Richard Rasker
Starting Member
  • Total Posts : 60
  • Reward points : 0
  • Joined: 2013/02/14 09:03:07
  • Location: 0
  • Status: offline
2019/07/23 04:18:35 (permalink)
0

MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is correct

Hello,
A somewhat annoying problem pops up when programming a PIC16LF1828 (IDE  = MPLAB X v5.20, programmer = PICkit 4, VDD = 3V):
Connecting to MPLAB PICkit 4...

Currently loaded versions:
Application version............00.04.15
Boot version...................01.00.00
Script version.................00.02.97
Script build number............117b21ad10
Target voltage detected
Target Device ID (0x28c0) is an Invalid Device ID. Please check your connections to the Target Device.

 
This is rather strange, since 0x28c0 is absolutely the correct Device ID.
Luckily, I can choose to ignore this and continue , and the device is programmed correctly subsequently, but it is annoying all the same. Does anyone know why this happens? Or is this one of several versioning bugs in MPLAB X v5.20 (I also encountered those DFP problems that require manual editing of older configurations.xml files)?
 
Thanks for any insights,
 
Best regards,
 
Richard
#1

12 Replies Related Threads

    Jim Nickerson
    User 452
    • Total Posts : 6117
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/23 07:04:28 (permalink)
    0
    Do you have a PicKit 4 "D" or "P" ? ( I was not aware there are two different versions nor how to tell them apart )
    They seem to have different levels of support for your chip 
     edit: add comments in parens
    post edited by Jim Nickerson - 2019/07/23 07:10:26

    Attachment(s)

    Attachments are not available: Download requirements not met
    #2
    Richard Rasker
    Starting Member
    • Total Posts : 60
    • Reward points : 0
    • Joined: 2013/02/14 09:03:07
    • Location: 0
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/23 07:16:20 (permalink)
    0
    Hi Jim,
    Thank you for your suggestion, but I don't think that the PICkit 4 has anything to do with it.
    I also tested this with the PICkit 3, and I'm getting the exact same message. I can't recall having had this issue before, when developing the first application with the PIC16LF1828, almost two years ago.
     
    So I still think that it's a bug in MPLAB X 5.20.
    #3
    Jim Nickerson
    User 452
    • Total Posts : 6117
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/23 07:17:52 (permalink)
    +2 (2)
    It looks like "D" means Debugging, "P" programming
    That would seem to indicate it is Beta support for debugging your chip and Green, full tested for programming
    Your results seem to indicate otherwise.
    Maybe it is time to open a support ticket
    #4
    NorthGuy
    Super Member
    • Total Posts : 5536
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/23 07:19:27 (permalink)
    +1 (1)
    "D" is for debugging
    "P" is for programming
     
    @OP:
     
    If you specified the device correctly, this is obviously some sort of bug in PICkit4. I would suggest reporting this to Microchip.
     
    #5
    NorthGuy
    Super Member
    • Total Posts : 5536
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/23 07:22:12 (permalink)
    +1 (1)
    Richard Rasker
    I can't recall having had this issue before, when developing the first application with the PIC16LF1828, almost two years ago.



    May be something new. There was a post recently where a poster had problems with id for PIC16F1829. Definitely contact Microchip and report this problem.
    #6
    Jim Nickerson
    User 452
    • Total Posts : 6117
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/23 07:45:05 (permalink)
    +1 (1)
    Interesting the "pack" seems to say "A828"

    <?xml version="1.0" encoding="UTF-8" standalone="no"?><edc:PIC xmlns:edc="http://crownking/edc" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" edc:acname="AC244063" edc:arch="16Exxx" edc:desc="" edc:dosid="01220" edc:dsid="40001419" edc:informedby="DOS PS DS" edc:isextended="false" edc:masksetid="LE033" edc:name="PIC16LF1828" edc:procid="0xA828" edc:psid="40001390" xsi:schemaLocation="http://crownking/edc edc/PIC.xsd">

    edit: get formatting right

    Attachment(s)

    Attachments are not available: Download requirements not met
    #7
    Richard Rasker
    Starting Member
    • Total Posts : 60
    • Reward points : 0
    • Joined: 2013/02/14 09:03:07
    • Location: 0
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/23 07:45:13 (permalink)
    0
    Hm, it's not MPLAB X 5.20 either - I fired up v5.15 with PICkit 3, and still get the same message.
     
    I don't know if there's a common cause, but this isn't exactly the first device support issue I've experienced in the past months. I think I'll stay away from any MPLAB updates for the time being, because I really need a working development environment ...
    #8
    TJvV
    New Member
    • Total Posts : 9
    • Reward points : 0
    • Joined: 2014/05/21 01:27:05
    • Location: 0
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/29 00:07:45 (permalink)
    0
    Just a simple question before blaming the tools: are you sure you selected the right chip in your project configuration?
     
    I've had similar issues in the past where the actual chip being programmed and the one selected were different versions of the same type (ex. low-power vs normal).
    In these cases, programming works the same, but they have different DEV IDs.
     
    In this case it could be PIC16F1828 instead of PIC16LF1828 in the project, seeing as the chip identifies as PIC16LF1828 as expected.
    #9
    JPortici
    Super Member
    • Total Posts : 703
    • Reward points : 0
    • Joined: 2012/11/17 06:27:45
    • Location: Grappaland
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/29 00:45:46 (permalink)
    +1 (1)
    JANickerson
    Do you have a PicKit 4 "D" or "P" ? ( I was not aware there are two different versions nor how to tell them apart )
    They seem to have different levels of support for your chip 
     edit: add comments in parens




    Sarcasm? Because they have always been the status of support for "Debug" and Program"
    #10
    Richard Rasker
    Starting Member
    • Total Posts : 60
    • Reward points : 0
    • Joined: 2013/02/14 09:03:07
    • Location: 0
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/29 02:22:55 (permalink)
    0
    Just a simple question before blaming the tools: are you sure you selected the right chip in your project configuration?

    Absolutely. Yes, I have made that mistake on occasion, but always spotted it in seconds. This is different -- the error message also didn't occur at first (some 6 months ago), but only reared its head recently, when making a minor change in a parameter on PCB's that were already programmed.
     
    But thanks for the reply anyway, as in many cases, the error is indeed quite simple.
    #11
    PStechPaul
    Super Member
    • Total Posts : 2342
    • Reward points : 0
    • Joined: 2006/06/27 16:11:32
    • Location: Cockeysville, MD, USA
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/29 12:02:31 (permalink)
    0
    In that case, I would suspect a subtle hardware issue related to the minor change you made to the PCBs. Layout is usually not too critical, but resistance and capacitance on the programming circuit is the "usual suspect". The previous batch may have been "on the edge" and this minor change finally "broke the camel's back". Perhaps you can read resistance and capacitance on the PICkit connector to detect differences, and also observe waveforms when trying to communicate.

     
    #12
    Richard Rasker
    Starting Member
    • Total Posts : 60
    • Reward points : 0
    • Joined: 2013/02/14 09:03:07
    • Location: 0
    • Status: offline
    Re: MPLAB X v5.20: "Target Device ID (0x28c0) is an Invalid Device ID" - yet the ID is cor 2019/07/30 02:09:14 (permalink)
    0
    Nope, the hardware can't be the problem either. The programming pins are not connected to anything else, with the exception of Vpp, which has a 10K resistor to VDD -- but the error message persists after removing this resistor.
    The connections between the device and the PICkit are also as clean as can be: 1" of PCB tracks to a small IDC connector, with a 4" ribbon cable to the PICkit 4, with no convoluted routing or the likes. Total capacitance per line is ~20 pF, which should be perfectly fine. The DSO shows rise and fall times of 10-12 ns without significant ringing, which is also what I'd expect.
     
    But thanks for the suggestion, it's always good to check these things out, if only to eliminate them as a possible cause.
    #13
    Jump to:
    © 2019 APG vNext Commercial Version 4.5