CODEGRIP with Starter Clicker 2 PIC32MZ

[gstanley]

Both CODEGRIP and NECTO cannot find target MCU.

We originally used ADAPT when we should have gotten ADAPT V4 with the CODEGRIP.
- Could applying Ground to PGC and PGD potentially Damage Target MCU (communications)?
- Could applying P7 to MCLR potentially damage Target MCU (communications)?

I updated CODE GRIP to firmware 1.5.0
CODEGRIP has POWER, USB-LINK and ACTIVE LEDs glowing.
Clicker 2 PIC32MZ2048EFH100 has green POWER LED glowing.
Mounted One Shot Clicker has orange PAUSE and green POWER LEDs glowing.

I tried installing on a different PC
I even tried every combination of communications rates (500k-4MHz]
I tried both 4-Wire and 2-Wire EJTAG Protocals (I think 2-Wire is correct)
I purchased and installed ADAPT V4.

CODEGRIP Suite Scanning DOES Detect CODEGRIP Programmer & Debugger (USB icon is/turns "BLUE")
CODEGRIP Suite PIC32MZ2048EFH100 Fails to DETECT MCU and messages "Connecting to target failed."

Please Advise

CodeGrip-PIC32MZ AdaptV4.jpg (753.95 KiB) Viewed 1154 times

Clicker 2 Communications Header.jpg (1.84 MiB) Viewed 1154 times

[filip]

Hi,

First of all I presume that the CODEGRIP programmer is detected by the CODEGRIP Suite application ?

Regards,
Filip.

[gstanley]

Yes, CODEGRIP Suite detects Code Grip (Note Blue USB icon )

[gstanley]

AFTER updated CODEGRIP to firmware 1.5.0 and using ADAPT V4 cable, I decided to try to connect using my old PC. I now CAN detect / find Target MCU my OLD PC. My new PC has a company installed and managed antivirus COMODO. I will have them provided me an outside network COMODO free machine for development work. I hope this is the end of my CODEGRIP / MCU communications problems.

[filip]

Hi,

I'm glad that you have managed to solve your issue!

Regards,
Filip.

[gstanley]

I need help again. I am on the same PC which "FOUND THE TARGET MCU" last Friday. Using CODEGRIP Suite, clicking DETECT gets "Connecting to Target Failed". I don't get it. This old PC does not have COMODO antivirus. Still, CODEGRIP is selected and found when "SCANNING" devices. USB is the current interface; its icon is blue. CODEGRIP can't find the target MCU, which is selected (PCI32MZ2048EFH100 matching chip part number marking). I have recycled PC power, with and without CODE GRIP connected (via USB 3). I have Cycled power on Clicker 2 board individually. As earlier posted, all LEDS indicate systems go. I don't know how to reload firmware 1.5.0, which should not be necessary. Realize after I first loaded 1.5.0 CODEGRIP the TARGET MCU WAS found. Are there any WINDOWS 10 settings I should have in place? This does not make sense. I also tried to access the boards using NECTO, but it too can't find the target either. I also have logged into my "account" using NECTO. It is still on trial activation. We have ordered the full NECTO Studio (with Mikro C AI) license, but I have not gotten the Activation key yet. I don't think that matters. My company has ordered me another LAPTOP for these development purposes. It will not have security software, for "sandbox" development. We are making a big commitment to MikroE. PLEASE HELP.