chipKIT® Development Platform

Inspired by Arduino™

Killed a Max32 while using PICkit3?

Created Wed, 29 Feb 2012 15:22:52 +0000 by peplin


Wed, 29 Feb 2012 15:22:52 +0000

I just received my first PICkit3 and I'm attempting to debug some code on a chipKIT Max32 (using the guide from KeithV here: )

Unfortunately I seemed to have killed one of my Max32 boards. Using MPLAB X, the PICkit3 was detected fine and I was able to use it to program the board a few times. Debugging wasn't working yet, but it seemed to be working to a certain degree.

Then suddenly I can still connect to the PICkit3, but when plugged into the board it reports:

Connecting to MPLAB PICkit 3...
Firmware Suite Version.....01.26.92
Firmware type..............PIC32MX

Target detected
Failed to get Device ID

I can't program it from MPIDE either, but that's probably because it doesn't have the stock bootloader anymore (since I had overwritten it with MPLAB).

I have another Max32 that still works fine, so I know the problem isn't the PICkit or my computer setup. Something's wrong with the board - some Googling led me to some folks saying this error means the PICkit isn't getting the most basic of responses from the MCU, so it's probably dead.

My question is can I resucue the Max32, and how did it die? I'm was fairly careful about plugging the PICkit3 in the correct orientation, but it's certainly possible I did it backwards - could that have fried the MCU?



Mon, 05 Mar 2012 16:31:17 +0000


Most Device ID errors are a result of improper connections to the programmer, or failure to power the target, leaving it unable to properly connect to the IDE. For more information regarding the debugging of Device ID issues, please see the PICkit 3 documentation.

Aside from this, an error has recently been reported related to the Programmer-To-Go button located on the PICkit 3 when used with the PIC32MX795 family. More details can be seen in this forum post: [url][/url].

If this button is pressed without a program image loaded into the device, the PICkit 3 may corrupt the device, leaving it unable to re-connect to the programmer. Currently, there is no way to recover the device once this has happened.

Our Development Tools team is currently working on replicating this issue. Once confirmed, they will work on developing a fix, which may come in the form of a firmware patch for the PICkit 3. I can't comment on the time-frame in which this will be completed, as this is still under investigation by the group.

We do not believe the ICD 3 is impacted by this issue and is a possible alternative. If continuing to use the PICkit 3, two temporary safe-guards to prevent this from occurring on accident, is to block the button as suggested in the forum post above, or open the device and remove the button itself.

Unfortunately if this is the case with your device, the PIC32 chip will need to be replaced to recover your damaged MAX32.

Regards, Josh


Mon, 05 Mar 2012 16:39:02 +0000

Thanks, Josh - when I wasn't having any luck with the programmer, I do remember trying that button. The documentation doesn't really say anything about it, just that it's reserved for "future use". I will tape over the buttons on our PICkit 3's so nobody else on team repeats my mistake.


Wed, 26 Sep 2012 23:17:07 +0000

HI, I have been the same with the MPLAB, however, after several tries I can program the bootloader, and re-recognize the device ID, but if I try another program it no longer recognize it. and apparently when the bootloader is loaded, do not do it properly because I can not schedule with mpide

have to change the micro pic32 ?