• AVR Freaks

Hot!ICD3 not recognised

Page: 12 > Showing page 1 of 2
Author
Ron Hayes
Super Member
  • Total Posts : 1340
  • Reward points : 0
  • Joined: 2003/11/07 12:38:10
  • Location: Ontario, Canada
  • Status: offline
2020/05/21 01:00:54 (permalink)
0

ICD3 not recognised

I started having trouble with my ICD3 , it kept crapping out when programming and now MPLABX (5.10 thru 5.4) doesn't even recognize it.. Windows 10 sees it and the driver is installed.
I've uninstalled the driver and reinstalled it multiple times with different versions.
 
I plugged it into my laptop and it sees it just fine so there is something with the PC setup MPLABX doesn't like.
 
And idea what I can do to get it working again?
#1

29 Replies Related Threads

    RISC
    Super Member
    • Total Posts : 5776
    • Reward points : 0
    • Status: offline
    Re: ICD3 not recognised 2020/05/21 02:58:58 (permalink)
    0
    Hi,
    I see in MPLAB X v5.40 (and probably earlier versions) a menu to force firmware update :
    Debug > (last line) Hardware Tool Emergency Boot Firmware Recovery
    Maybe you want to try this ?
    Regards
    NB : sometimes the firmware update takes place more easily when the debugger is not attached to the target but only to the PC
    #2
    NKurzman
    A Guy on the Net
    • Total Posts : 18909
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: offline
    Re: ICD3 not recognised 2020/05/21 08:06:57 (permalink)
    0
    CISAR only supports ICD4 and PICKit4 now.
     
    But if you think they should fix it, And the F/W reload does not help:
    https://www.microchip.com/cisar/Home.aspx
    #3
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/21 12:10:28 (permalink)
    0
    I went back to 5.10 it has this same recovery option but only accepts ICD4 and PicKit4.
     
    I don't feel there's anything wrong with the ICD since it works fine on my laptop. Somethings changed in MPLAB to stop looking for it. I'm not buying an ICD4, this is just a hobby.
    #4
    DevMod1
    Administrator
    • Total Posts : 532
    • Reward points : 0
    • Joined: 2009/02/10 09:34:30
    • Location: 0
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 09:24:09 (permalink)
    +2 (2)
    If you have every used the old MPLAB 8.xx that uses a different driver for the ICD3 so you may have to use the driver switcher so your ICD3 can be seen by MPLAB X

    _____________________________

    Please read the forum posting guidelines. Do not double post, please help keep these forums professional and comments respectful.
    Please notify the moderators of problems/spam/trolls.
    #5
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 13:21:06 (permalink)
    0
    I tried that but since I don't have the old mplab installed it exited out.
     
    I tried to uninstall the driver but as soon as I plug it back in it automatically knows where to look for the driver and installs it.
    On my laptop I made a dummy project just to increment a var, programmed a chip and stepped through it. it works just fine. so the ICD isn't bricked.
     
    For some reason MPLAB is ignoring the device. Tried installing 4 different version of the driver too..
    Ron
    post edited by Ron Hayes - 2020/05/22 14:38:52
    #6
    RISC
    Super Member
    • Total Posts : 5776
    • Reward points : 0
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 15:22:07 (permalink)
    0
    Ron,
    It is never necessary to play "with" drivers on MPLAB X...they are automatically installed during installation and there is no reason to change them. I use MPLAB X for many years and I don't even know where the drivers are, even though I also had from time to time issues with ICD3.
    Can you please connect only the ICD3 to your PC and show us the error messages ?
    Is it enumerated ?  Check the USB peripherals in the Windows system. Is ICD3 or any Microchip device visible ?
    You may want to use the freeware USBdeview to more easily see Microchip debuggers
    Regards
     
    #7
    Ken_Pergola
    Super Member
    • Total Posts : 2245
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 16:37:59 (permalink)
    0
    Hello Ron,
     
    Expanding upon what 'DevMod1' indicated, have you tried the MPLAB Device Driver Switcher?
     
    Example, on my Windows 10 PC the executable to it lives here (change v5.xx accordingly):
    C:\Program Files (x86)\Microchip\MPLABX\v5.40\Switcher\64Bit\MPDDSwitch64.exe
     
    Please see the attached screen shot for details.
     
    This should be quick to try to see if this solves your problem.
     
    Best regards,
     
    Ken

    Attached Image(s)

    #8
    Ken_Pergola
    Super Member
    • Total Posts : 2245
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 16:48:43 (permalink)
    +1 (1)
    Hello Ron,
     
    Another option is to collect some data from the 'USB Tool Connection Diagnostics' utility and post it here.
     
    It's a plug-in so you need to install it first.
     
    Then after installing it you can run it via the MPLAB X IDE menu and click the 'Start Diagnostics' icon and paste the results here in the forum:
     
    MPLAB X IDE 'Tools' --> 'Embedded' -- > 'USB Tool Connection Diagnostics' menu item
     
    Please see attached screen shot for installing the plug-in.
     
    Best regards,
     
    Ken
     
     

    Attached Image(s)

    #9
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 17:05:03 (permalink)
    0
    RISC
    Ron,
    It is never necessary to play "with" drivers on MPLAB X...they are automatically installed during installation and there is no reason to change them. I use MPLAB X for many years and I don't even know where the drivers are, even though I also had from time to time issues with ICD3.
    Can you please connect only the ICD3 to your PC and show us the error messages ?
    Is it enumerated ?  Check the USB peripherals in the Windows system. Is ICD3 or any Microchip device visible ?
    You may want to use the freeware USBdeview to more easily see Microchip debuggers
    Regards
     


     I was wondering if a new driver broke it.. so I rolled them back, I had to do something!
    There is no error message, windows device manager shows it installed and says it's functioning properly.
     
    Also Flashed the firmware on the ICD3 to see if that was an issue, it was not.
    post edited by Ron Hayes - 2020/05/22 17:10:59

    Attached Image(s)

    #10
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 17:17:07 (permalink)
    0
    ==============================================================================
    Initializing examination: Done
    Plug-in version: 1.0.8
    ==============================================================================
    OS version: Windows 10 (10.0)
    ==============================================================================
    OS architecture: 64-bit
    ==============================================================================
    MPLAB X IDE version: 5.40
    ==============================================================================
    MPLAB X communications library version: 3.37.03
    Bridge library version: 3.42
    Bridge library extended version: Build:64:0000:342:20190717
    Tool discovery method: Normal
    ==============================================================================
    JVM: 1.8.0_202 64-bit
    ==============================================================================
    Examine Support Library (or Libraries):
       C:\Windows\system32\winusb.dll: Found
          Permissions: E R W
                 Size: 28160 bytes
             Loadable: Yes
       C:\Windows\system32\drivers\winusb.sys: Found
          Permissions: E R W
                 Size: 105472 bytes
       C:\Windows\system32\libusb0.dll: Found
          Permissions: E R W
                 Size: 76384 bytes
             Loadable: Yes
       C:\Windows\system32\drivers\libusb0.sys: Found
          Permissions: E R W
                 Size: 52832 bytes
    ==============================================================================
    Examine Bridge Library:
       C:\Windows\system32\USBAccessLink_3_42.dll: Found
          Permissions: E R W
                 Size: 259072 bytes
             Loadable: No: java.lang.UnsatisfiedLinkError: Native Library C:\Windows\System32\USBAccessLink_3_42.dll already loaded in another classloader
                       Not an error. Already opened by IDE.
    ==============================================================================
    Examine PnP Support Application:
       C:\Windows\system32\mchpwinusbdevice64.exe: Found
          Permissions: E R W
                 Size: 261632 bytes
    ==============================================================================
    Examine Port Definition File:
       C:\Windows\system32\mchpdefport: Found
          Permissions: E R W
                 Size: 40 bytes
       Port Definition File Info:
          Host: localhost
          Port: 30000
    ==============================================================================
    Accessing Attached Tools:
       Selection: MPLABComm-USB(04D8:03EB),ThirdParty()
       Retrieving tool list:
          [0]: :=MPLABComm-USB-Microchip:=<vid>0000:=<pid>0000:=<rev>0000:=<man>?:=<prod>?:=<sn>?:=<drv>x:=<xpt>b:=end
       Tool communication:
          ######################################################################
          [0]: :=MPLABComm-USB-Microchip:=<vid>0000:=<pid>0000:=<rev>0000:=<man>?:=<prod>?:=<sn>?:=<drv>x:=<xpt>b:=end
          Get tool... OK
          NOTE: Unit is plugged in.
          :==== Device Descriptor ===========:
                           bLength=0
                   bDescriptorType=0
                           wUsbRev=0
                      bDeviceClass=0x0
                   bDeviceSubClass=0x0
                   bDeviceProtocol=0
                 bEP0MaxPacketSize=0
                         wVendorId=0x0000
                        wVroductId=0x0000
                        wDeviceRev=0x0000
          bManufacturerStringIndex=0
               bProductStringIndex=0
          bSerialNumberStringIndex=0
           bNumberOfConfigurations=0
          :==== Configuration Descriptor ====:
          ERROR: Configuration descriptor null.
          :==== Manufacturer ================:
          not available
          :==== Product =====================:
          not available
          :==== Serial Number ===============:
          not available
          :==== Endpoint List ===============:
          ERROR: GetEndpointList() failed.
          :==== Connect/Disconnect ==========:
          Connecting... OK
          Disconnecting... OK
          Release tool... Result=0 (No error.)
    ==============================================================================
    Releasing examination: Done
    _
    #11
    David
    Pic User
    • Total Posts : 1307
    • Reward points : 0
    • Joined: 2007/12/17 23:19:53
    • Location: uk sussex
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 17:23:55 (permalink)
    0
    Have you tried to program another device / pcb ? could the target be broken ?

    David
    I support http://picforum.ric323.com because this forum is often too broken to use!
    #12
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 22:31:56 (permalink)
    0
    David
    Have you tried to program another device / pcb ? could the target be broken ?


    Like I mentioned I programed a device on my laptop so I know it works. On the PC I can't even see the device in MPLAB, yet windows shows it just fine.
     
    Ron
    #13
    Ken_Pergola
    Super Member
    • Total Posts : 2245
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: ICD3 not recognised 2020/05/22 23:17:52 (permalink)
    0
    Hello Ron,
     
    Thank you for taking the time to run the 'USB Tool Connection Diagnostics' plug-in.
     
    Several things look amiss to me:
          :==== Configuration Descriptor ====:
          ERROR: Configuration descriptor null.

          :==== Endpoint List ===============:
          ERROR: GetEndpointList() failed.
     
    Let me forward this 'USB Tool Connection Diagnostics' to the proper person to see if it may lead to a resolution for you.
     
    Best regards,
     
    Ken
    #14
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/23 22:06:24 (permalink)
    0
    Thank you.
     
    Its strange that MPLAB can't pull this info in
    MPLABComm-USB-Microchip:=<vid>0000:=<pid>0000:=<rev>0000:

    #15
    Ken_Pergola
    Super Member
    • Total Posts : 2245
    • Reward points : 0
    • Joined: 2003/11/07 12:48:48
    • Status: offline
    Re: ICD3 not recognised 2020/05/24 00:58:24 (permalink)
    0
    Hi Ron,
     
    Yes, I think those issues are the proverbial "smoking gun" as to why you are having an issue only on that particular computer only. Based on the data you posted it does not look like a systemic MPLAB ICD 3 hardware issue so far otherwise it would not work on your laptop.
     
    I made the request for the proper person to look at your USB diagnostics log. There will probably be a post here when there is anything substantive to report (or further questions to ask) next week.
     
    Happy Memorial Day weekend.
     
    Best regards,
     
    Ken
     
    P.S. I was thinking on my bike ride. You have been involved in these forums for many years. Have you had the desire to take things to the next level and go beyond calling this 'just a hobby'?
    #16
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/24 11:47:13 (permalink)
    0
    It has been a while, started in 96 with the 16F84...Lol
     
    I have had jobs where I used my experience but doing it as a job take a lot of the fun out of it. I prefer to do things on my own timeline and continue to enjoy it. I enjoy my full time gig as a wireman.
     
    Thanks for your help in this matter.
    #17
    prj
    Super Member
    • Total Posts : 218
    • Reward points : 0
    • Joined: 2009/12/01 14:35:45
    • Location: 0
    • Status: offline
    Re: ICD3 not recognised 2020/05/26 09:11:50 (permalink)
    +1 (1)
    All zeros in the USB info indicates that Windows could not collect the data properly. A note from Microsoft reads:
     
    Typically when the USB driver stack fails to enumerate a device, the hub driver still reports the arrival of the device to Windows and the USB device is marked as an unknown device in Device Manager. The device has a Device ID of USB\VID_0000&PID_0000 and a Hardware ID and Compatible ID of USB\UNKNOWN. The following events cause the USB hub driver to enumerate a USB device as an unknown device:
    • A port reset request timed out during enumeration.
    • The Set Address request for the USB device failed.
    • The request for the USB device's Device Descriptor failed.
    • The USB Device Descriptor was malformed and failed validation.
    • The request for the Configuration Descriptor failed.
    • The USB Configuration Descriptor was malformed and failed validation.
    end quote
    How does the tool show up in the Device Manger at this point? (I apologize if you already said but I missed it).
    #18
    prj
    Super Member
    • Total Posts : 218
    • Reward points : 0
    • Joined: 2009/12/01 14:35:45
    • Location: 0
    • Status: offline
    Re: ICD3 not recognised 2020/05/26 09:15:33 (permalink)
    +1 (1)
    Additionally, is the port into which the ICD3 is plugged a USB 3 port? At times, Windows may turn off the USB 2 compatibility of a port (causes can vary: system updates, IS flight of fancy, etc). 
     
    Also, this is not plugged into a dock, correct? Just into the PC itself?
     
    Thanks.
     
    #19
    Ron Hayes
    Super Member
    • Total Posts : 1340
    • Reward points : 0
    • Joined: 2003/11/07 12:38:10
    • Location: Ontario, Canada
    • Status: offline
    Re: ICD3 not recognised 2020/05/26 10:49:08 (permalink)
    0
    I posted pictures higher up in the thread of device manager. It reports as functioning properly.
     
    I think I tried both 2 and 3. I'd have to check and see if my case USB ports are 2 or 3, I'm not home at the moment. I'll get back to you.
    #20
    Page: 12 > Showing page 1 of 2
    Jump to:
    © 2020 APG vNext Commercial Version 4.5