Hot!ICD3 Bricking my PIC32MZ2048EFM144's?

Author
chipmonk
Starting Member
  • Total Posts : 37
  • Reward points : 0
  • Joined: 2012/01/23 07:20:30
  • Location: 0
  • Status: offline
2017/10/11 15:41:51 (permalink)
0

ICD3 Bricking my PIC32MZ2048EFM144's?

So I have boards I have been programming and runnjing in debug mode for the past week and a half but now they seem to just have all died, they all output this message when I try to run them in debug mode, program with MPLABX IDE v4.01 or even to connect with IPE v4.01
 
Connecting to MPLAB ICD 3...
Currently loaded firmware on ICD 3
Firmware Suite Version.....01.50.04
Firmware type..............PIC32MZ
Target voltage detected
Unable to connect to the target device.
Failed to get Device ID
 
I have a deadline for tuesday, thats 5 days away. How does this happen? Capacitors, cable length and all are according to specifications! I connected the PICkit3 as well and I get the same message. My PIC32MZ2048EFM144 is device revision A1. 
 
Must I buy new chips? what causes this problem? How do I buy device revision A2 chips? GOD HELP US..........MICROCHIP U SURE GIVE US A TOUGH TIME.
#1

13 Replies Related Threads

    chipmonk
    Starting Member
    • Total Posts : 37
    • Reward points : 0
    • Joined: 2012/01/23 07:20:30
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/11 15:57:07 (permalink)
    0
    All boards that have this chip are giving me same error, so I reckon buying new chips wont change anything? Not sure but, this is really bad
    #2
    NKurzman
    A Guy on the Net
    • Total Posts : 14848
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/11 16:01:58 (permalink)
    3 (1)
    1. Try an older version of MPLab. (3.51)
    2. Try erasing them with IPE
    3.verify that it is not something on the pcb blowing the chips.
    #3
    Larry.Standage
    Super Member
    • Total Posts : 745
    • Reward points : 0
    • Joined: 2011/12/30 09:50:47
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/11 16:02:36 (permalink)
    3 (1)
    Are these on starter kits? If so, have you disconnected the tiny jumper that connects the PKOB to the processor?
    #4
    chipmonk
    Starting Member
    • Total Posts : 37
    • Reward points : 0
    • Joined: 2012/01/23 07:20:30
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/11 17:02:52 (permalink)
    0
    NO they are not starter kits, let me try iunstalling an older versiuon of MPLAB
    #5
    chipmonk
    Starting Member
    • Total Posts : 37
    • Reward points : 0
    • Joined: 2012/01/23 07:20:30
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 06:03:31 (permalink)
    0
    So I installed MPLABX v3.50, still the problem persists.  Ive raised a ticket with microchip, but in the meantime, are there alot of people using the PIC32MZ chips? Seems people hate harmony, am I paying for jumping onto the PIC32MZ harmony wagonwheel? Must I just ditch this and quickly make a new design (still wont meet my deadline)
    #6
    chipmonk
    Starting Member
    • Total Posts : 37
    • Reward points : 0
    • Joined: 2012/01/23 07:20:30
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 06:06:34 (permalink)
    0
    Hey, 
     
    Thanks for the suggestions, but how do I erase with the IPE, well coz the board wont connect to the IPE. PCBs are fine nothing to blow PICs, connected new PCBs and still the error persists
    #7
    NKurzman
    A Guy on the Net
    • Total Posts : 14848
    • Reward points : 0
    • Joined: 2008/01/16 19:33:48
    • Location: 0
    • Status: online
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 06:48:10 (permalink)
    3 (1)
    You do not need to uninstall one MPLabX to install a different one. IPE connects to the icd , but not the board? With what message? It sounds like you may have an issue with your board. I have not heard of anyone with a similar issue.
    #8
    NorthGuy
    Super Member
    • Total Posts : 4460
    • Reward points : 0
    • Joined: 2014/02/23 14:23:23
    • Location: Northern Canada
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 07:30:35 (permalink)
    3 (1)
    May be you just fried your ICD?
    #9
    chipmonk
    Starting Member
    • Total Posts : 37
    • Reward points : 0
    • Joined: 2012/01/23 07:20:30
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 09:33:39 (permalink)
    0
    Thanks, so the ICD works, tested it with the board its shipped with. My were boards assembled in china, I did specify that they buy all components from Digikey, do you reckon I have counterfiet chips? How do chips work, and the just randomly stop working? I dont get it, cannot be right, well if I never managed to connect to the boards that would have been understandable. 
    #10
    maxruben
    Super Member
    • Total Posts : 3097
    • Reward points : 0
    • Joined: 2011/02/22 03:35:11
    • Location: Sweden
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 11:58:10 (permalink)
    0
    Check the PGD and PGC pins with an oscilloscope. See if there are any slow fall- or risetimes or voltages "half-" high or low.
     
    If you have the possibility, try with another ICD (or Real ICE). Or any other programmer.
     
    /Ruben
    #11
    Sobottech
    Senior Member
    • Total Posts : 115
    • Reward points : 0
    • Joined: 2015/12/02 03:32:17
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 13:01:14 (permalink)
    3 (1)
    This Pic got different ICSP-Pins
     
    "2.4 ICSP Pins
     
    The PGECx and PGEDx pins are used for ICSP and debugging purposes. It is recommended to keep the trace length between the ICSP connector and the ICSP pins on the device as short as possible. If the ICSP connector is expected to experience an ESD event, a series resistor is recommended, with the value in the range of a few tens of Ohms, not to exceed 100 Ohms. Pull-up resistors, series diodes and capacitors on the PGECx and PGEDx pins are not recommended as they will interfere with the programmer/debugger communications to the device. If such discrete components are an application requirement, they should be removed from the circuit during programming and debugging. Alternatively, refer to the AC/DC characteristics and timing requirements information in the respective device Flash programming specification for information on capacitive loading limits and pin input voltage high (VIH) and input low (VIL) requirements. Ensure that the “Communication Channel Select” (i.e., PGECx/PGEDx pins) programmed into the device matches the physical connections for the ICSP to MPLAB® ICD 3 or MPLAB REAL ICE™. For more information on ICD 3 and REAL ICE connection requirements, refer to the following documents that are available from the Microchip web site."
     
    So check your Communication Channel Select. Perhaps you changed something accidentally.
     
    Was something changed on Hardware? are there pull-ups resistors, diodes, capacitors ... on the programming pins?
    Other hardware issues? short circuits...
    Is the pic getting hot? how many mA is the PIC taking?
    What was changed in Hardware or Software during programmable Pic and the mentioned problems?
    #12
    dan1138
    Super Member
    • Total Posts : 2584
    • Reward points : 0
    • Joined: 2007/02/21 23:04:16
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/12 16:49:15 (permalink)
    0
    chipmonk
    Thanks, so the ICD works, tested it with the board its shipped with. My were boards assembled in china, I did specify that they buy all components from Digikey, do you reckon I have counterfeit chips? How do chips work, and the just randomly stop working? I don't get it, cannot be right, well if I never managed to connect to the boards that would have been understandable.

    Testing the ICD3 with a known good target is useful first step but there are some issues that occur.
     
    This is a rare thing but it has happened to me once. My ICD3 worked fine with my Microchip Explorer16 and my product PCB then it failed on my product just like your experience. The Explorer16 responded fine. I was using a PIC32MX so I tried it with MPLAB v8.92. This forces a driver switch and a reload of all of the ICD3 firmware. That got it working with both boards. I switched back to MPLABX (with a driver switch and firmware reload) and it continues to work. Make of this what you can but it seems that a forced reload of the ICD3 firmware seemed to fix this for me. I know this is anecdotal but the forced firmware reload "should" be a simple exercise.
     
    I have had a similar issue with a PICkit3 where the ESD protection devices on VPP, PGC and PGD got a little damaged and replacing them fixed it.
     
    Good luck.
    #13
    chipmonk
    Starting Member
    • Total Posts : 37
    • Reward points : 0
    • Joined: 2012/01/23 07:20:30
    • Location: 0
    • Status: offline
    Re: ICD3 Bricking my PIC32MZ2048EFM144's? 2017/10/13 09:49:55 (permalink)
    0
    Sounds real promising mate, thank you, will try that
    #14
    Jump to:
    © 2017 APG vNext Commercial Version 4.5