chipKIT® Development Platform

Inspired by Arduino™

Bootloader reprogrammer issue

Created Thu, 13 Oct 2011 09:54:41 +0000 by huberthu


Thu, 13 Oct 2011 09:54:41 +0000


As recently I bought another ChipKit Uno32 board, I test it with loading a blink example. But I got a failure message. I search it on the forum. And I found it was due to the timing issue in the new Microchip chip.

Then I try to load the latest firmware arduino-bootloader.X.Uno32_8-19-11.hex. I downloaded it from Digilent official website. I use ICD2 with MPLAB IDE v8.76

I 've got a programming error:

Connecting to MPLAB ICD 2 ...Connected Setting Vdd source to target Target Device [color=#BF0040]PIC32MX320F128H[/color] found, revision = Rev 0x50900053 ...Reading ICD Product ID Running ICD Self Test ...Passed MPLAB ICD 2 ready for next operation Programming Target... ...Validating configuration fields ...Erasing Part ...Loading Program Executive ...Programming Boot Config (0x1FC00000 - 0x1FC001FC) ...Verifying Boot Config memory (0x1FC00000 - 0x1FC001FC) ...Programming Boot Config (0x1FC00400 - 0x1FC01BFC) ...Verifying Boot Config memory (0x1FC00400 - 0x1FC01BFC) ICD0296: Failed CRC check (Mem='BootConfig' Expected=0x1064 Received=0x14A8) ICD0275: Programming failed. MPLAB ICD 2 ready for next operation

I've tried this on two boards and all give me the same error message. I think the HEX file may be wrong.

Please help.

Many thanks,




Fri, 14 Oct 2011 08:18:36 +0000

The problem I've got is the same as described in thread with my new purchased chipkit


I try to load the latest bootloader supposed to fix the above problem with ICD2 and MPLAB IDE v8.76.

I couldn't get the programming through. I've selected device as PIC32MX320F128H. I select power from the device. Then I import the hex file and load it into the chip. It stops at BOOT config memory.

Any one can help.

I've got two chipkit board at the same situation.


Mon, 17 Oct 2011 07:52:57 +0000

I'm surprised no one knows about it. Any suggestion please.


Tue, 18 Oct 2011 14:50:03 +0000

It all just work for me, but I use a PICkit3, not a PICkit2. There could be unknow issues with that. Since it failed on 2 boards, I suspect there is something you don't have set up correctly, or the PICkit2 just might not work.

However, the only thing I might suggest is that you use external power. I know for sure that the PICkit3 can not power the chipKIT, and that debug connector is not intended to power the board.

The PICkit3 is compatible enough that you can use the USB cable typically used by MPIDE to power the chipKIT (if you don't have an external power supply). However you must recoginize that both MPIDE and the PICkit3 are going to "fight" for the reset line. The PICkit3 will win, and when used in a normal manner both the PICkit3 and MPIDE USB cable can be concurrently plugged in. The worse case senerio is that MPIDE may not be able to upload if the PICkit3 is holding the reset line.

Again, I do not use a PICkit2, so I have no idea what the differences might be.


Tue, 18 Oct 2011 20:53:08 +0000

I used pickit2 (stand alone SW not with MPLAB ) without any problems to reload bootloader on a Uno32. you need to add 6 ICSP pins (permanently or just pushed in ) and make sure latest device file is available.


Fri, 21 Oct 2011 12:47:51 +0000


Thanks for the reply. But I'm using ICD2 not Pickit2. I power the chipkit UNO32 seperately by a USB lead.

Now I suspect this is something wrong with my ICD2. As I'm usign the latest MPLAB v8.76, I did a firmware upgrade for the ICD2. Maybe the new firmware doesn't support the pic32mx320f128h well.

Jacob Christ

Sat, 29 Oct 2011 19:22:02 +0000

What happens if you instead of programming the chip read out its contents then verify back against what was just read out?

Also, you might look at the program memory once it's been read out to see if it looks like machine code or nonsense.

I've seen read back issues with the ICD3, but the bootloader still worked after I programmed it.

The FTDI drives the MCLR line of the uC and I've found that this sometimes messes with the programming of the chip as well.



Mon, 31 Oct 2011 17:08:08 +0000

The problem is with ICD2, and is associated with the same issue the bootloader has. PicKIT3, ICD3, and RealICE will all work just fine.

If you are unable to get one of the other tools to reprogram the new Bootloader, contact Digilent customer service and they'll help you out!