• AVR Freaks

Helpful ReplyHot!Failed to initialize ICD 4 - Brand new unit

Author
Jeremy Brown
Starting Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/01/27 18:17:07
  • Location: Denver, CO
  • Status: offline
2019/04/08 13:16:34 (permalink)
0

Failed to initialize ICD 4 - Brand new unit

I have been trying to use my new ICD 4, and no matter what I do, MPLAB X IDE just says Failed to initialize ICD 4. I can connect to the ICD 4 in MPLAB X IPE, and I can program the PIC32MZ2064DAH169 Starter Kit, but it just fails to initialize every time in the IDE. I really wanted to be able to debug using the ICD 4, but I cannot get it to do anything in the IDE. I do not have IPE open while I am trying to program the device in the IDE, the ICD 4 is connected to a 9V 3A power supply, and the USB hub the ICD 4 is connected to is externally powered. Does anyone have any idea why it would work in IPE and not in the IDE? I have tried restarting my iMac Pro multiple times, restarting the IDE, unplugging and replugging the ICD 4, all with the same result that it fails to initialize. Even when I click to Register the ICD 4 in the IDE, it has the same message. I am using MPLAB X v5.15. Even doing a self test with the test board connected has the same result, failed to initialize.
#1
MHS
Super Member
  • Total Posts : 358
  • Reward points : 0
  • Joined: 2010/04/23 10:05:39
  • Location: 0
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/08 13:19:00 (permalink)
0
Make sure you're disconnected from the IPE. Does it fail even with the IPE closed? My guess is that the IPE would be hogging the ICD4 while the IDE is trying to talk to it.
#2
Jeremy Brown
Starting Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/01/27 18:17:07
  • Location: Denver, CO
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/08 15:10:11 (permalink)
5 (1)
It fails even with IPE closed.
 
The only other diagnostic message I get is:
 
The programmer could not be started: Could not connect to tool hardware: ICD4Tool, com.microchip.mplab.mdbcore.ICD4Tool.ICD4ToolBase
post edited by Jeremy Brown - 2019/04/08 15:28:07
#3
typematrix
New Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/03/04 08:11:26
  • Location: 0
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/08 15:56:26 (permalink) ☄ Helpfulby Jeremy Brown 2019/05/04 13:31:25
0
Do you have access to a windows or Linux machine?
#4
mpgmike
Super Member
  • Total Posts : 365
  • Reward points : 0
  • Joined: 2014/01/23 17:27:06
  • Location: NJ
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/08 18:28:07 (permalink)
0
Slim chance, but when I got mine, it looked like the programming pins on the 6-pin programming adapter (don't have the part number in front of me) were reversed.  I couldn't get it to work.  Before making a stink on the forum (or with Microchip) I decided to hook it up "backwards".  What do you know, it worked!  I was, however, getting the test module to work; it uses the RJ485 connector.
#5
mpgmike
Super Member
  • Total Posts : 365
  • Reward points : 0
  • Joined: 2014/01/23 17:27:06
  • Location: NJ
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/08 18:28:19 (permalink)
0
Slim chance, but when I got mine, it looked like the programming pins on the 6-pin programming adapter (don't have the part number in front of me) were reversed.  I couldn't get it to work.  Before making a stink on the forum (or with Microchip) I decided to hook it up "backwards".  What do you know, it worked!  I was, however, getting the test module to work; it uses the RJ485 connector.
#6
Jeremy Brown
Starting Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/01/27 18:17:07
  • Location: Denver, CO
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/08 23:14:51 (permalink)
0
In MPLAB X, the relay that clicks when it connects to the PIC32 doesn't even click when I try to program the device, or run the program or debug the program. Trying to register the device also says "Failed to initialize". Whereas when I clicked Register for a PicKit4 a few minutes later, that successfully registered to my account.
 
In IPE, it will connect to the PIC32 MZ DA Starter kit, it gets the serial number, and then waits for further commands. When I try to program it in IPE, it erases the memory and instantly programs the device.  Using the same Starter kit board and programming interface board, with the PicKit 4 hooked to it, it works fine in the IDE, but when I plug in the RJ-11 cable from the ICD 4, it won't do anything in the IDE
post edited by Jeremy Brown - 2019/04/09 09:04:01
#7
mpgmike
Super Member
  • Total Posts : 365
  • Reward points : 0
  • Joined: 2014/01/23 17:27:06
  • Location: NJ
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/09 08:01:37 (permalink)
0
Another thing, the USB cable is touchy on mine.  I had to wiggle it to get it to connect.
#8
MShouk
New Member
  • Total Posts : 28
  • Reward points : 0
  • Joined: 2012/05/19 00:52:26
  • Location: Chandler, Arizona
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/09 09:57:47 (permalink)
0
Hello Jeremy. What version of MPLAB are you using?
#9
NKurzman
A Guy on the Net
  • Total Posts : 18266
  • Reward points : 0
  • Joined: 2008/01/16 19:33:48
  • Location: 0
  • Status: online
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/09 11:50:53 (permalink)
5 (1)
If you think it is Just Broken:
https://www.microchip.com/cisar/Home.aspx
#10
Jeremy Brown
Starting Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/01/27 18:17:07
  • Location: Denver, CO
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/10 15:49:25 (permalink)
0
MPLAB X v5.15
 
And i don't think it is broken, because it can program the device in IPE.
#11
prj
Super Member
  • Total Posts : 214
  • Reward points : 0
  • Joined: 2009/12/01 14:35:45
  • Location: 0
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/04/30 11:13:31 (permalink)
0
Which OS X are you running? Thanks.
#12
Jeremy Brown
Starting Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/01/27 18:17:07
  • Location: Denver, CO
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/05/01 11:40:18 (permalink)
0
I am running macOS 10.14.4 with MPLAB X v5.15, XC32 v2.15 Pro, and Harmony v2.06.
 
I just tested the ICD4 in a Ubuntu 18.04.02 Parallels VM on my iMac Pro, and it works in Ubuntu with MPLAB X IDE for both debugging and programming. I went back to macOS and tried uninstalling MPLAB X, removing all settings and preferences, and then I reinstalled. Opened the IDE, installed MHC, restarted, opened my project, but it still doesn't work. I know that support is two yellow circles for my chip and the ICD4, is this possibly a known issue?
post edited by Jeremy Brown - 2019/05/04 13:29:01
#13
prj
Super Member
  • Total Posts : 214
  • Reward points : 0
  • Joined: 2009/12/01 14:35:45
  • Location: 0
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/05/07 09:25:58 (permalink)
0
Can you do a test for us? Have the ICD4 plugged into your Mac. With the IDE opened, please go to Tools->Plugins and on the Available Plugins tab, select and install the USB Tool Connection Diagnostics plug-in.
 
Invoke that plug-in from Tools->Embedded, selecting the plug-in. In the plug-in icon menu, select the third icon down (looks like a check list). This will run the diagnostics. Once it is done, you can select the last icon in the menu which will copy the output to the clipboard. Please paste that output here (it is text -- you may need to make sure the line feeds are properly represented). If the ICD4 can be seen properly at this level, then the USB comm portion is at least working.
 
Thanks.
#14
Jeremy Brown
Starting Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/01/27 18:17:07
  • Location: Denver, CO
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/05/10 11:14:12 (permalink)
0
==============================================================================
Initializing examination: Done
==============================================================================
OS version: Mac OS X (10.14.4 Mojave)
==============================================================================
OS architecture: 64-bit (x86_64)
==============================================================================
MPLAB X IDE version: 5.15
==============================================================================
MPLAB X communications library version: 3.35.04
Bridge library version: 3.33
==============================================================================
JVM: 1.8.0_181 64-bit
==============================================================================
Examine Support Library (or Libraries):
  Symbolic link matches expected target file:
  Symbolic Link:
   /Applications/microchip/MPLABX/v5.15/mplab_platform/bin/libUSBAccessLink_3_33.dylib: Found
      Permissions: E R notW
             Size: 173872 bytes
         Loadable: No: java.lang.UnsatisfiedLinkError: Native Library /Applications/microchip/mplabcomm/v3.35.04/lib/libUSBAccessLink_3_33.dylib already loaded in another classloader
                   Not an error. Already opened by IDE.
  Expected Target:
   /Applications/microchip/mplabcomm/v3.35.04/lib/libUSBAccessLink_3_33.dylib: Found
      Permissions: E R notW
             Size: 173872 bytes
         Loadable: No: java.lang.UnsatisfiedLinkError: Native Library /Applications/microchip/mplabcomm/v3.35.04/lib/libUSBAccessLink_3_33.dylib already loaded in another classloader
                   Not an error. Already opened by IDE.
  Actual Target:
   /Applications/microchip/mplabcomm/v3.35.04/lib/libUSBAccessLink_3_33.dylib: Found
      Permissions: E R notW
             Size: 173872 bytes
         Loadable: No: java.lang.UnsatisfiedLinkError: Native Library /Applications/microchip/mplabcomm/v3.35.04/lib/libUSBAccessLink_3_33.dylib already loaded in another classloader
                   Not an error. Already opened by IDE.
------------------------------------
  File: /Applications/microchip/mplabcomm/v3.35.04/lib/libusb-1.0.0.dylib
     Found
   /Applications/microchip/mplabcomm/v3.35.04/lib/libusb-1.0.0.dylib: Found
      Permissions: E R notW
             Size: 69872 bytes
==============================================================================
Examine Bridge Library:
   /Applications/microchip/mplabcomm/v3.35.04/lib/libUSBAccessLink_3_33.dylib: Found
      Permissions: E R notW
             Size: 173872 bytes
         Loadable: No: java.lang.UnsatisfiedLinkError: Native Library /Applications/microchip/mplabcomm/v3.35.04/lib/libUSBAccessLink_3_33.dylib already loaded in another classloader
                   Not an error. Already opened by IDE.
==============================================================================
Examine PnP Support Application:
  Symbolic link matches expected target file:
  Symbolic Link:
   /etc/.mplab_ide/mchpmacusbdevice: Found
      Permissions: E R notW
             Size: 21652 bytes
  Expected Target:
   /Applications/microchip/mplabcomm/v3.35.04/lib/mchpmacusbdevice: Found
      Permissions: E R notW
             Size: 21652 bytes
  Actual Target:
   /Applications/microchip/mplabcomm/v3.35.04/lib/mchpmacusbdevice: Found
      Permissions: E R notW
             Size: 21652 bytes
==============================================================================
Examine Port Definition File:
  File: /etc/.mplab_ide/mchpdefport
     Found
   /etc/.mplab_ide/mchpdefport: Found
      Permissions: E R W
             Size: 40 bytes
  Content:
    localhost
    30000
    30002
    30004
    30006
    30008
==============================================================================
Accessing Attached Tools:
   Selection: MPLABComm-USB(04D8:03EB),ThirdParty()
   Retrieving tool list:
      [0]: :=MPLABComm-USB-Microchip:=<vid>04D8:=<pid>9015:=<rev>0100:=<man>Microchip Technology Incorporated:=<prod>MPLAB ICD 4:=<sn>JIT180810548:=<drv>x:=<xpt>b:=end
   Tool communication:
      ######################################################################
      [0]: :=MPLABComm-USB-Microchip:=<vid>04D8:=<pid>9015:=<rev>0100:=<man>Microchip Technology Incorporated:=<prod>MPLAB ICD 4:=<sn>JITxxxxxxxxx:=<drv>x:=<xpt>b:=end
      Get tool... OK
      NOTE: Unit is plugged in.
      :==== Device Descriptor ===========:
                       bLength=18
               bDescriptorType=1
                       wUsbRev=512
                  bDeviceClass=0x0
               bDeviceSubClass=0x0
               bDeviceProtocol=0
             bEP0MaxPacketSize=64
                     wVendorId=0x04D8
                    wVroductId=0x9015
                    wDeviceRev=0x0100
      bManufacturerStringIndex=1
           bProductStringIndex=2
      bSerialNumberStringIndex=3
       bNumberOfConfigurations=1
      :==== Configuration Descriptor ====:
      0000: 09 02 2E 00 01 01 00 C0 FA 09 04 00 00 04 FF FF ................
      0010: FF 00 07 05 81 02 00 02 00 07 05 02 02 00 02 00 ................
      0020: 07 05 83 02 00 02 00 07 05 04 02 00 02 00 __ __ ..............
      :==== Manufacturer ================:
      stringIndex=1
          content='Microchip Technology Incorporated'
      :==== Product =====================:
      stringIndex=2
          content='MPLAB� ICD 4'
      :==== Serial Number ===============:
      stringIndex=3
          content='JITxxxxxxxxx'
      :==== Endpoint List ===============:
      EP=0x81, Size=0x200, Type=Bulk, Dir=IN
      EP=0x2, Size=0x200, Type=Bulk, Dir=OUT
      EP=0x83, Size=0x200, Type=Bulk, Dir=IN
      EP=0x4, Size=0x200, Type=Bulk, Dir=OUT
      :==== Connect/Disconnect ==========:
      Connecting... OK
      Disconnecting... OK
      Interface subtool 0 not available.
      Release tool... Result=0 (No error.)
==============================================================================
Releasing examination: Done

 
I got the exact same result from both the replacement ICD4 that Microchip sent me, and the faulty one that I am sending back. However the difference between the two is the replacement they sent me works in macOS in the IDE for debugging and programming, and the one I am sending back will only program the device in IPE on macOS. I would really like to thank Microchip for their timely response to my incident report, as I am nearing the final stages of development on my current project with a PIC32MZ2064DAH, and the project is getting to a size where PKOB debugging is just way too slow, so the working ICD4 replacement could not have come at a better time.
post edited by Jeremy Brown - 2019/06/05 11:41:10
#15
prj
Super Member
  • Total Posts : 214
  • Reward points : 0
  • Joined: 2009/12/01 14:35:45
  • Location: 0
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/05/13 08:56:33 (permalink)
0
Glad to hear that the replacement is working for you.
Just to clarify: The USB tool diagnostics you posted was for the failing unit, correct? I am concerned about the serial number (JITxxxxxxx). This obviously is not a valid serial number for a tool, though the correct serial number shows up earlier in the diagnostic (JIT180810548), so that is a bit confusing.
#16
Jeremy Brown
Starting Member
  • Total Posts : 13
  • Reward points : 0
  • Joined: 2019/01/27 18:17:07
  • Location: Denver, CO
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2019/05/16 15:36:23 (permalink) ☄ Helpfulby mpgmike 2019/05/20 21:21:31
0
Oh, i just kind of blocked that out, I didn't know if I was supposed to post that, but I guess I missed a spot.
 
I am really impressed with the response while debugging a large Harmony/FreeRTOS PIC32MZ2064DAH application with the ICD4, I was waiting three or more minutes to hit a breakpoint on the PicKIT4, but it hits it in 5-10 seconds on the ICD4 (which with the delays I had to use in code is very close to real time). I don't have an ICD3 to compare against, but the ICD4 is a huge step up from the PicKIT4.
post edited by Jeremy Brown - 2019/05/16 15:56:37
#17
RDS Cliff
Junior Member
  • Total Posts : 63
  • Reward points : 0
  • Joined: 2016/09/23 11:50:05
  • Location: 0
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2020/01/23 00:32:39 (permalink)
0
Jeremy:  Did you find a solution?  I'm experiencing the same problem.  I've been switching back and forth between MPLAB X v5.30 and v5.10.  I've been playing around with some of the ICD4xxx.jar files in v5.30 but it's v5.10 that has the error message:
 
Could not connect to tool hardware: ICD4Tool, com.microchip.mplab.mdbcore.ICD4Tool.ICD4ToolBase
 
I've swapped ICD4s but it didn't help.  MPLAB X v5.30 still works with limitations.  Just wondering if I accidently moved or deleted a file.
#18
RDS Cliff
Junior Member
  • Total Posts : 63
  • Reward points : 0
  • Joined: 2016/09/23 11:50:05
  • Location: 0
  • Status: offline
Re: Failed to initialize ICD 4 - Brand new unit 2020/01/23 16:37:10 (permalink)
0
I reverted my project configurations.xml file with my version control and it fixed the problem.  New lines added by v5.30 were:

<property key="ToolFirmwareFilePath"
value="C:\Program Files (x86)/Microchip/MPLABX/v5.30/mplab_platform/mplablibs/modules/ext/icd4armfiles.jar/ICD4FW_000188.jam

which I was screwing around with and...
 
<property key="communication.interface.jtag" value="2wire"/>
 
So one of those lines did it.  All fixed now.
#19
Jump to:
© 2020 APG vNext Commercial Version 4.5