Hot!Target Device ID (0x0) is an Invalid Device ID.

Page: 123 > Showing page 1 of 3
Author
Roberttku
New Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2018/05/10 20:44:37
  • Location: 0
  • Status: offline
2018/05/18 09:43:50 (permalink)
0

Target Device ID (0x0) is an Invalid Device ID.

Hi All,
 
OS: Win10
MCU:PIC16F877A
MPLAB X IDE v4.05
PICKIT3 Version: v3.10
XC8 Version : v1.45
I've tried many solution that I founded from web, but still can't solve the issue of "Target Device ID (0x0) is an Invalid Device ID. Please check your connections to the Target Device.".
Who know what's reason, kindly tell me, please.
This issue confused me over 1week.
 
Sincerely,
Robert 
#1

51 Replies Related Threads

    du00000001
    Just Some Member
    • Total Posts : 2180
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/18 11:22:30 (permalink)
    +1 (1)
    Either the target is unpowered or the communications link is wrong or broken.
    • Did the target (board) ever work?
    • Which programming/debugging tool are you using? Is the self-test executing properly?

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #2
    Mysil
    Super Member
    • Total Posts : 2892
    • Reward points : 0
    • Joined: 2012/07/01 04:19:50
    • Location: Norway
    • Status: online
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/18 12:40:32 (permalink)
    +1 (1)
    Hi,
    If you have used the PICkit 3 with
    PICkit 3.10 Programmer Application, or with MPLAB 8.92,
    strange things may happen, causing Device ID (0x0).
     
    You may go to PICkit 3.10 Programmer Application, and use 'Tools' 'Revert to MPLAB', 
    See also PICkit 3 Programmer Application User Guide, it is available thru 'Help' menu.
     
    Or use MPLAB 8.92, and do a Manual Firmware Update of the PICkit 3 tool.
     
    There are a total of 3 firmware pieces in PICkit 3, and MPLAB X doesn't always get it right.
     
       Mysil
    #3
    Roberttku
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2018/05/10 20:44:37
    • Location: 0
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/20 18:59:30 (permalink)
    0
    Hello Mysil,
     
    Thanks for replying.
     'Tools'--> 'Revert to MPLAB' can't choose, because it's gray not black. What can I do?
    You mentioned "MPLAB X doesn't always get it right.", so you suggest use MPLAB 8.92 rather than MPLAB X when with PICKIT 3.
     
    Sincerely,
     
    Robert
     
    #4
    Mysil
    Super Member
    • Total Posts : 2892
    • Reward points : 0
    • Joined: 2012/07/01 04:19:50
    • Location: Norway
    • Status: online
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/20 20:01:04 (permalink)
    +1 (1)
    Hi,
    What I tried to say:
    Use MPLAB 8.92 to do a manual Firmware update on the PICkit 3.
    Close MPLAB 8.92 and then start MPLAB X.
    When you then Program or Debug in MPLAB X, it will know what is needed. Hopefully.
     
    When the correct firmware get in place, then MPLAB x and PICkit 3 work with all PIC devices I have at hand,
    from PIC12F1822 and PIC16F930, PIC16F886 and PIC16F18875, PIC18F14K22, PIC18F26K22,
    thru PIC24 and dsPIC33... to PIC32MX460, PIC32MX795 and PIC32MZ...
     
    Or use MPLAB 8.92 with PIC16F877A, it is vintage computing anyway.
     
    Regards,
       Mysil
    #5
    Aussie Susan
    Super Member
    • Total Posts : 3357
    • Reward points : 0
    • Joined: 2008/08/18 22:20:40
    • Location: Melbourne, Australia
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/20 20:03:04 (permalink)
    +1 (1)
    I'm not sure why Mysil brought MPLAB into this thread but the combination of the MPLABx and PicKit3 that you are using should be fine.
    This question really belongs in the "Programmers" sub-forum where you will find a large number of very similar (actaully, the same) questions.
    Check the wiring and check that there are no extraneous connections on the connections to the PicKit3. Also look at the PicKit3 User Guide.
    Susan
    #6
    Roberttku
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2018/05/10 20:44:37
    • Location: 0
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/21 18:19:18 (permalink)
    0
    Hello du00000001,
     
    Either the target is unpowered or the communications link is wrong or broken.
    • Did the target (board) ever work?
        -->No,  the target (board) never work. I changed MCU 3ea and rewired many times, but still didn't work. My wiring of PICkit 3 fully followed PICkit 3 Programmer/Debugger User’s Guide Page 20/FIGURE 2-4. The board didn't work as well.
     
    • Which programming/debugging tool are you using? Is the self-test executing properly?
    --> programming/debugging tool  is PICkit 3. Is the self-test executing for PICkit 3??
     
    Sincerely,
    Robert
    #7
    du00000001
    Just Some Member
    • Total Posts : 2180
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/21 19:55:11 (permalink)
    +1 (1)
    OK - maybe you should provide your schematics. Especially when the board never worked ...
    At least you seem to have VDD now.
    I have to admit: not sure about the availability of the self test on the PICkit3
     
    I'm often using a "naked" PIC16Fxxx - only a capacitor between VDD and VSS, the PIC powered from a PICkit3.
    As your (antique) PIC16877A doesn't work without a proper oscillator, this minimalist setup won't work with your controller. OTOH it might be a good idea to start with checking whether the oscillator is working. Hope you've got an oscilloscope ...

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #8
    qɥb
    Monolothic Member
    • Total Posts : 3329
    • Reward points : 0
    • Joined: 2017/09/09 05:07:30
    • Location: Jupiter
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/21 20:07:27 (permalink)
    +2 (2)
    You don't need an oscillator to read the device ID, or to program.
    Only when you come to run, or debug your code, do you need it to oscillate...
     

    This forum is mis-configured so it only works correctly if you access it via https protocol.
    The Microchip website links to it using http protocol. Will they ever catch on?
    PicForum "it just works"
    #9
    du00000001
    Just Some Member
    • Total Posts : 2180
    • Reward points : 0
    • Joined: 2016/05/03 13:52:42
    • Location: Germany
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/21 20:29:20 (permalink)
    +1 (1)
    @ qhb
    What are the minimum prerequisites - beyond proper supply and proper connection to PICkit (/MCLR, PGD, PGC) ? Anything else?

    PEBKAC / EBKAC / POBCAK / PICNIC (eventually see en.wikipedia.org)
    #10
    qɥb
    Monolothic Member
    • Total Posts : 3329
    • Reward points : 0
    • Joined: 2017/09/09 05:07:30
    • Location: Jupiter
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/21 20:41:14 (permalink)
    +2 (2)
    There is one more "gotcha" for a PIC16F877A.
    The RB3/PGM pin must be pulled low.
    If it is floating, sometimes the programmer will work, and sometimes it won't.
    Also, it shouldn't need saying, but power must be connected to BOTH pairs of Vss/Vdd pins.
     

    This forum is mis-configured so it only works correctly if you access it via https protocol.
    The Microchip website links to it using http protocol. Will they ever catch on?
    PicForum "it just works"
    #11
    Roberttku
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2018/05/10 20:44:37
    • Location: 0
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/22 20:34:53 (permalink)
    0
    Hello du00000001 & qɥb,

    To clarified root causes, I found a LED circuit to try as attched file. No matter how I tried, still didn't work.
    Error message is "Target Device ID (0x0) is an Invalid Device ID. Please check your connections to the Target Device."
    Floowing are my test item:
    1. RB3/PGM(Pin 36)-->Connect GND
    2. Remove/change a new OSC
     
    In addition, I found two strange questions:
    As user guide Item 2.4.3 said "The recommended source of power is external and derived from the target application."
    A.Connected external power(5V) and power off it, error message are
     1. Too much current has been drawn on VDD. Please disconnect your circuit, check the CLK and DATA lines for shorts and then reconnect.
    2. Target Device ID (0x0) is an Invalid Device ID. Please check your connections to the Target Device.
     
    B.Connected external power(5V) and power on it, error message are
    1. The target circuit may require more power than the debug tool can provide. An external power supply might be necessary.
    Connection Failed.
    2. Target Device ID (0x0) is an Invalid Device ID. Please check your connections to the Target Device.
     
     
    Sincerely,
    Robert
     
     

    Attached Image(s)

    #12
    qɥb
    Monolothic Member
    • Total Posts : 3329
    • Reward points : 0
    • Joined: 2017/09/09 05:07:30
    • Location: Jupiter
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/22 20:58:04 (permalink)
    +2 (2)
    That schematic shows a wire connecting MCLR to VPP.
    Did you leave that out (you must).
     
    If your programmer is displaying "Too much current drawn on VDD", then it must have been set to supply power to the PIC. Turn that OFF if you are supplying external power.
    If you do, then it should report "connected" as soon as you apply power to the PIC, then try to read the ID.
     

    This forum is mis-configured so it only works correctly if you access it via https protocol.
    The Microchip website links to it using http protocol. Will they ever catch on?
    PicForum "it just works"
    #13
    Roberttku
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2018/05/10 20:44:37
    • Location: 0
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/22 21:10:33 (permalink)
    0
    Hello qɥb,
     
    Thanks for promptly replying.
    That schematic shows a wire connecting MCLR to VPP.
    Did you leave that out (you must).
    -->I connected MCLR to VDD. You said"Did you leave that out (you must).". Is mean to MCLR can't connect VDD.
     
    "must have been set to supply power to the PIC" 
    -->How does set supply power to the PIC.
     
    Sincerely,
     

    Robert

    #14
    qɥb
    Monolothic Member
    • Total Posts : 3329
    • Reward points : 0
    • Joined: 2017/09/09 05:07:30
    • Location: Jupiter
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/22 21:14:15 (permalink)
    +2 (2)
    Yes. You must NOT connect MCLR to VDD.
    The programmer must be able to lift the VDD pin to 13V to put the chip into programming mode.
    That wire will prevent this from happening. It is effectively shorting out the 10k resistor.
     

    "must have been set to supply power to the PIC" 
    -->How does set supply power to the PIC.

    It's somewhere in the PICkit3 settings in MPLABX.
    You need to turn that setting OFF, so the PK3 does NOT try to power the circuit.
     

    This forum is mis-configured so it only works correctly if you access it via https protocol.
    The Microchip website links to it using http protocol. Will they ever catch on?
    PicForum "it just works"
    #15
    Roberttku
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2018/05/10 20:44:37
    • Location: 0
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/22 21:28:43 (permalink)
    +1 (1)
    Hello qɥb,
     
    Oh, My God. It works. I,m really really want to say "Thank you very much*100 times."
     
    Sincerely,
     
    Robert
    #16
    Roberttku
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2018/05/10 20:44:37
    • Location: 0
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/24 18:55:46 (permalink)
    0
    Hello qɥb,
     
    It's somewhere in the PICkit3 settings in MPLABX.
    -->Is captured image as attached file?
     
    Sincerely,
    Robert

    Attached Image(s)

    #17
    qɥb
    Monolothic Member
    • Total Posts : 3329
    • Reward points : 0
    • Joined: 2017/09/09 05:07:30
    • Location: Jupiter
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/24 19:14:33 (permalink)
    +1 (1)
    Almost
     

    Attached Image(s)


    This forum is mis-configured so it only works correctly if you access it via https protocol.
    The Microchip website links to it using http protocol. Will they ever catch on?
    PicForum "it just works"
    #18
    PStechPaul
    Super Member
    • Total Posts : 2063
    • Reward points : 0
    • Joined: 2006/06/27 16:11:32
    • Location: Cockeysville, MD, USA
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/24 22:19:31 (permalink)
    0
    I have found that you can set the PIC voltage to 4.75 or so and this will often allow connecting it to the target and powering it, when the target's power is disconnected. Some 7805 type regulators will draw current if 5V is applied to its output.

     
    #19
    Roberttku
    New Member
    • Total Posts : 25
    • Reward points : 0
    • Joined: 2018/05/10 20:44:37
    • Location: 0
    • Status: offline
    Re: Target Device ID (0x0) is an Invalid Device ID. 2018/05/27 18:02:14 (permalink)
    0
    Hello qɥb,
    Are the PICKIT3 of Pin2 & 3 need to connect Target Board of VDD and GND?
     
    Sincerely,
    Robert
     
    #20
    Page: 123 > Showing page 1 of 3
    Jump to:
    © 2018 APG vNext Commercial Version 4.5