• AVR Freaks

Hot!Getting Target Device ID (0x0) on Explorer 16 board

Page: 12 > Showing page 1 of 2
Author
dvtronic
Starting Member
  • Total Posts : 44
  • Reward points : 0
  • Joined: 2018/10/19 05:51:28
  • Location: 0
  • Status: online
2020/01/15 12:10:55 (permalink)
0

Getting Target Device ID (0x0) on Explorer 16 board

I'm using an Explorer 16 devt board with a PIC24FJ256GB110 PIM.  When I attempt to download firmware onto this device via MPLAB X IDE, I keep getting a "Target Device ID (0x0) is an Invalid Device ID" error message. All of the electrical connections appear to be solid, so I don't know what might be causing this.  Any advice?

I did verify that the slider switch is set to PIM rather than PIC.
#1

20 Replies Related Threads

    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 09:28:40 (permalink)
    0
    Update: Using a scope, I verified that there's activity on the PICkit 3's PGC (clock) and PGD (data) lines.  Still, the device ID is reported as 0x0, even though the data and clock lines suggest otherwise.  Any idea what's going on?
     
    #2
    Jim Nickerson
    User 452
    • Total Posts : 6430
    • Reward points : 0
    • Joined: 2003/11/07 12:35:10
    • Location: San Diego, CA
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 09:42:17 (permalink)
    #3
    NorthGuy
    Super Member
    • Total Posts : 5881
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 09:53:23 (permalink)
    5 (1)
    Verify that you have selected the correct device in your project.
    #4
    jtemples
    عُضْوٌ جَدِيد
    • Total Posts : 11526
    • Reward points : 0
    • Joined: 2004/02/13 12:31:19
    • Location: Southern California
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 10:16:41 (permalink)
    0
    And verify that the PIM is plugged in correctly.
    #5
    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 11:45:48 (permalink)
    0
    I did verify that I have the proper microcontroller selected and that the PIM is seated firmly.

    I took a closer look at the PGC/PGD signals, and this is what I'm getting. I see that the MCHP (0x4D434851) is being transmitted correctly.  However, the /MCLR signal isn't behaving as expected.  It it strobed before the MCHP is sent, but then it goes high again before the MCHP even begins to be transmitted.  Any idea what might be causing this?
     
     
    post edited by dvtronic - 2020/01/16 12:01:57

    Attached Image(s)

    #6
    NKurzman
    A Guy on the Net
    • Total Posts : 18191
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 12:05:02 (permalink)
    0
    What Version of MPLabX?
    How is the Board Powered?
     
    #7
    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 13:47:17 (permalink)
    0
    Using MPLAB X IDE 5.25 and an external 9V power supply.
    #8
    NorthGuy
    Super Member
    • Total Posts : 5881
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 15:36:34 (permalink)
    0
    MCLR must be low during the "MCHP" sequence, then it should go high. This is opposite to what you see. Looks like a bug. I would suggest reporting it to Microchip.
    #9
    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 15:38:58 (permalink)
    0
    If it's a bug, it's a pretty severe one.  How would this device ever work?

    Does the PICKit 3 require different firmware depending on which family of microcontroller it's talking to?
    #10
    ric
    Super Member
    • Total Posts : 25244
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 15:55:32 (permalink)
    0
    dvtronic
    Does the PICKit 3 require different firmware depending on which family of microcontroller it's talking to?

    Yes. It downloads new firmware into the PK3 each time you program with a different family to what is currently in it.

    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!
    #11
    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 15:59:42 (permalink)
    0
    Okay, so the download process should be automatic. That's consistent with what I read in the documentation. Is it possible that it's using the wrong firmware somehow?

    When I attempt to connect, I get the following message. I'm using a PIC24FJ256GB110 though, and this wording doesn't seem right. (Yes, I did verify that a PIC24FJ256GB110 is selected within the project properties in MPLAB X IDE.) 


    Connecting to MPLAB PICkit 3...
    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.56.00
    Firmware type..............dsPIC33F/24F/24H
    #12
    ric
    Super Member
    • Total Posts : 25244
    • Reward points : 0
    • Joined: 2003/11/07 12:41:26
    • Location: Australia, Melbourne
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 16:11:54 (permalink)
    0
    You can force a complete refresh of the PK3 firmware by holding down the button on the PK3 as you connect its USB cable.
    Next time you attempt to program with it, you should see many update messages.
     

    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!
    #13
    NKurzman
    A Guy on the Net
    • Total Posts : 18191
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 17:16:24 (permalink)
    0
    If this is an MPLabX Bug then you will need to download and try V5.30 ( the current version) before reporting it , if case it has been fixed.
    #14
    dan1138
    Super Member
    • Total Posts : 3314
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 18:35:16 (permalink)
    0
    Is your Explorer-16 the DM240001 model?

    #15
    dan1138
    Super Member
    • Total Posts : 3314
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/16 18:51:49 (permalink)
    0
    The DM240001 requires an external device programmer.
     
    The RealICE on the 6-pin modular connector.
     
    The PICKit3 on 6-pin inline connector labeled PICKIT2 on my board.
     
    Are you using any other method to connect your PICKit3?
     
    #16
    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/17 07:11:49 (permalink)
    0
    @dan1138, I am indeed using a DM240001.  Using a PICkit3 with the 6-pin inline connector. This is the only way that I'm connecting to this board.
     
    #17
    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/17 09:50:28 (permalink)
    0
    NKurzman
    If this is an MPLabX Bug then you will need to download and try V5.30 ( the current version) before reporting it , if case it has been fixed.


    I upgraded to v5.30.  The PICkit 3 firmware suit is now at 01.56.02, but the problem remains. Sigh.
    #18
    dan1138
    Super Member
    • Total Posts : 3314
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/17 12:50:32 (permalink)
    4 (1)
    I have the same hardware you are using and did the same steps you have tried.

    Updating the PICKit3 firmware with the MPLABX IDE causes issues for me so I use the IPE tool.

    Using MPLABX v5.25 (not yet installed MPLABX v5.30) this is the log from using IPE tool:
    /*
    *****************************************************

    Connecting to MPLAB PICkit 3...

    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.51.06 *
    Firmware type..............dsPIC33F/24F/24H
    Now Downloading new Firmware for target device: PIC24FJ256GB110
    Downloading bootloader
    Bootloader download complete
    Programming download...

    Downloading RS...            <<<<<----- MPLABX IPE hangs at this step ----->>>>>
    Failed to download firmware  <<<<<----- Unpluged PICKit3 from USB     ----->>>>>

    PICkit 3 removed
    Connection Failed.


    <<<<<----- Pluged PICKit3 in to USB then reconnected the MPLABX IPE ----->>>>>
    *****************************************************

    Connecting to MPLAB PICkit 3...

    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.51.06 *
    Firmware type..............Unknown Firmware Type
    Now Downloading new Firmware for target device: PIC24FJ256GB110
    Downloading RS...
    RS download complete
    Programming download...

    Downloading AP...
    AP download complete
    Programming download...


    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.56.00
    Firmware type..............dsPIC33F/24F/24H
    Target voltage detected
    Target device PIC24FJ256GB110 found.
    Device Revision ID = 3
    */

    You can see it is working for me, but at this point the firmware that MLPABX loaded in to the PICKit3 may or may not be stable.

    Because my PICKit3 was using Firmware Suite Version.....01.51.06 the target specific firmware for the PIC24FJ256GB110 may be out of synch with Firmware Suite Version.....01.56.00.

    It is a good idea to cause the IPE to reload the target specific firmware for the PIC24FJ256GB110.

    I do this by disconnecting the PICKit3 from the DM240001, click disconnect in the IPE, select an 8-bit target like a PIC18F4550, click apply, click connect, then select my intended target PIC24FJ256GB110, click apply, click connect.
     
    The IPE log should look like this:
    /*
    *****************************************************

    Connecting to MPLAB PICkit 3...

    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.56.00
    Firmware type..............dsPIC33F/24F/24H
    Now Downloading new Firmware for target device: PIC18F4550
    Downloading AP...
    AP download complete
    Programming download...


    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.56.00
    Firmware type..............PIC18F
    Target device was not found (could not detect target voltage VDD). You must connect to a target device to use PICkit 3.


    *****************************************************

    Connecting to MPLAB PICkit 3...

    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.56.00
    Firmware type..............PIC18F
    Now Downloading new Firmware for target device: PIC24FJ256GB110
    Downloading AP...
    AP download complete
    Programming download...


    Currently loaded firmware on PICkit 3
    Firmware Suite Version.....01.56.00
    Firmware type..............dsPIC33F/24F/24H
    Target device was not found (could not detect target voltage VDD). You must connect to a target device to use PICkit 3.
    */

    #19
    dvtronic
    Starting Member
    • Total Posts : 44
    • Reward points : 0
    • Joined: 2018/10/19 05:51:28
    • Location: 0
    • Status: online
    Re: Getting Target Device ID (0x0) on Explorer 16 board 2020/01/20 11:42:29 (permalink)
    0
    Thank you, @dan1138.  If it's working for you, then I suspect that something has gone wrong with my hardware.  
    #20
    Page: 12 > Showing page 1 of 2
    Jump to:
    © 2020 APG vNext Commercial Version 4.5