ICD4 seen by MPLAB but cannot run self test nor programming the target - Page 1
Forum section: electronics / general

author: ricko_uk
author_rank: Super Contributor
timestamp: August 04, 2020, 04:47:41 pm
content: Hi,I installed MPLAB version 5.40 (downloaded yesterday) on a client's PC which does NOT have internet connection.In the project properties the ICD-4 appears and it does allow me to select it as debug tool.The ICD4 is recognised by windows when plugged in with no errors. But when clicking on "Run debugger/programmer self test" in the pop-up window where you select the tool the ICD-4 shows its serial number next to it but is disabled.There was a message at the ICD-4 window at the bottom which said something to do with online connection and/or registration specific to ICD-4 (not MPLAB). I clicked cancel and while doing so inadvertently selected "do not display this message again" so it does not appear again even if I restart MPLAB. So no idea what the exact message was.The ICD-4 is fully working (tested on another machine just now) and showing the blue light (i.e. stand by).I tried the following which didn't work:1) reinstalling everythingbut didn't work2) blocking MPLAB from the firewall so it does not tryto access the network which does not exist anyway but that didn't work either3) rebooting4) plugging and unplugging the ICD45) another perfectly working brand new ICD4How can I make it work?Any pointers?SIDE NOTE - PROBABLY IRRELEVANT - Also when compiling an empty project (standard microchip generated C++ project with NO code added at all) it takes 1:14 minutes to compile and the PC is quite a fast one so it cannot be the PC. I will make a separate post about this but I thought of mentioning it here too in case they are related.Many thanks

author: ricko_uk
author_rank: Super Contributor
timestamp: August 05, 2020, 04:48:16 am
content: Could anybody help pleaseAny suggestions are welcomed

author: ace1903
author_rank: Regular Contributor
timestamp: August 05, 2020, 07:13:10 am
content: I don't know what is the reason in this particular case but have experienced many problems with ICD4.Compared with earlier versions, ICD4 is total garbage. I noticed that it doesn't like USB hubs.On the PC at work were strange problems appeared we narrowed down that when USB3.0 self powered hub is used ICD4 doesn't work.Also be sure that you use power supply for ICD4. When powered from USB it doesn't report any problems but sometimes works sometimes not.I noticed that on some targets that are perfectly programmable with PICKIT3 with ICD4 programming behave erratically.On microchip forum some problems with programming circuit were reported and some solutions were proposed.I know that you are suspecting on network connection to be culprit but it is good to check other stuff also. ICD4 sucks at reporting errors.I spent hours trying to find why there are days when it works and days when it doesn't . Tried software updated downgrades fpga bitstreams....Half of the problems solved when I bought power supply for it. Don't know why Microchip sells it without PSU when without PSU ICD4 is unusable.I am satisfied with ICD1 ICD2 PICKIT2 PICKIT3 but ICD4 is unusable. Regret that I haven't bought ICD3 instead of ICD4.

author: jc101
author_rank: Frequent Contributor
timestamp: August 05, 2020, 08:15:49 am
content: I think these are all related to not having a network connection.Probably time to raise a support ticket with Microchip and see what they say.https://microchipsupport.force.com

author: ricko_uk
author_rank: Super Contributor
timestamp: August 05, 2020, 09:16:28 am
content: Thank you, I have.Attached are pictures of the various windows/messages in case someone has some ideas of what happens.

author: jc101
author_rank: Frequent Contributor
timestamp: August 05, 2020, 09:37:48 am
content: You could install USB Device Tree view from here (https://www.uwe-sieber.de/usbtreeview_e.html) and see what Windows thinks is actually plugged in...I have also had on a few occasions USB issues with Windows 10. I've ended up turning the PC off, and the PSU, pressing the power button to drain the PSU. Then turning it all back on again. Something left the USB ports in an odd state. I had to do that to bring back keyboards, mice, a RealICE, and an ICD4. Yesterday it was after adding a new USB Hub to my system, things were very odd until I did that. I gave up digging to see actually what was happening a while ago, but I've only ever had to do it with Windows systems.

author: hli
author_rank: Frequent Contributor
timestamp: August 05, 2020, 11:42:04 am
content: I think the recommendation is to connect ICD4 (and PK4 too) to a USB3 port. (Remember this from trying to upgrade the firmware upon first connection). Use a good quality cable too.

author: ricko_uk
author_rank: Super Contributor
timestamp: August 05, 2020, 01:03:33 pm
content: I am connecting it directly onto the PC, using only its USB cable.Why USB3? That PC does not have a USB3

author: hli
author_rank: Frequent Contributor
timestamp: August 05, 2020, 04:22:13 pm
content: Hmm, I just cannot find the reference I had anymore (was about a year ago or so) - only for the PK4 I cann find the USB 3 recommendation (https://microchipsupport.force.com/s/article/PICkit-4-troubleshooting). But I remember the same issue with updating the firmware, and this "reception on endpoint failed" error. And I ended up with this recommendation that for FW update (via the bootloader mode) an USB 3 should be used, and it worked after that. Maybe this has changed in the meantime (current manuals don't mention is anywhere), but I thought it might be worth a shot (connecting to different ports is always one of the troubleshooting steps).

author: ricko_uk
author_rank: Super Contributor
timestamp: August 05, 2020, 04:34:42 pm
content: Thank you hli!

author: NorthGuy
author_rank: Super Contributor
timestamp: August 05, 2020, 09:39:22 pm
content: Microchip will replace it if it's faulty.

author: ricko_uk
author_rank: Super Contributor
timestamp: August 05, 2020, 10:37:31 pm
content: Thank you NorthGuy,would that be the case even if I had it for few years (albeit used only a couple of times)?

author: Sal Ammoniac
author_rank: Super Contributor
timestamp: August 05, 2020, 10:53:15 pm
content: Why would you think it's faulty? If it works on another machine and another ICD4 doesn't work on the first machine, then it seems like an issue with the configuration of the first machine, not the ICD4, that's at fault.

author: NorthGuy
author_rank: Super Contributor
timestamp: August 05, 2020, 11:20:23 pm
content: Quote from: ricko_uk on August 05, 2020, 10:37:31 pmI don't know about PICkit4, but this always was their policy with earlier products.Quote from: Sal Ammoniac on August 05, 2020, 10:53:15 pm"another perfectly working brand new ICD4" seems to be an indication of that. Thus, it's either a firmware problem, or some sort of hardware fault.