Created Wed, 29 Jun 2011 06:59:18 +0000 by Ar Druid O
Wed, 29 Jun 2011 06:59:18 +0000
Whenever I try to program the max32 with the pickit3, it can't see the max32. Usually the error is "failed to get target ID". Do I have something configured incorrectly?
Wed, 29 Jun 2011 07:48:03 +0000
I got exactly the same problem here ... For fun i have connect my old pickit 2 (who can't program pic32mx7xxx) and he tell me a problem with vddcore. I have get that problem on a old dev board long time ago and was resolved in adding a 47uF capacitor between the vddcore and gnd pin. I have try that here but it don't work. If someone found a solution it will be great.
Wed, 29 Jun 2011 10:17:05 +0000
I assume you're supplying power to the chipKIT? I hook up USB to pickit3 and USB to chipKIT and then connect pickit3 to chipKIT.
The only thing I have noticed in MPLAB X is that I often have to go into project Properties->Conf->Hardware Tool and deselect/reselect the SN asociated with the pickit3 before this will work.
Connecting to MPLAB PICkit 3... Firmware Suite Version.....01.26.56 Firmware type..............PIC32MX Target detected Device ID Revision = 4300053 Programming... Programming/Verify complete
Thu, 30 Jun 2011 08:01:49 +0000
Thanks for your info Rich , i tried it but here it don't work :? I so cut the reset trace andf put a jumper to be sure too. So i tried with external power supply too ... With all of this test the pickit is not able to see the CPU. To be sure it is not the Pickit 3 i put a pic32mx795F512L PIM on the old board and burned the chipkit max32 firmware and then tried the StickOS firmware too , everything was ok ... I have now to look why i cant program the max32 board ... I just hope that the max32 board pic32 is not dead :roll: Do you know a simple test to see if the cpu is still alive or not ?
Thu, 30 Jun 2011 18:05:21 +0000
The only way that I have ever programmed an Uno32 or a Max32 is via a PICKit3. I designed the hardware and did some of the low level hardware checkout and used a PICKit3 for all of that. It is necessary to use a cable between the PICKit3 and the chipKIT board to make the connection, as the PICKit3 will physically interfere with the power connector or the USB connector when plugged in directly. I use a 6" six pin cable that we use with our Pmod peripheral module products. (we now have a kit with the cable and necessary connectors on our web site as an option for the chipKIT boards).
I've never had any problem connecting to any functional chipKIT board. The "failed to get target id" message means a communication failure between the PICKit3 and the PIC32 part. The most likely causes are: signal integrity in the connection (using too long of a cable, having too much series resistance in the connections, too much capacitance on the MCLR pin); the PIC32 chip not having power; or a malfunctioning PICKit3 or PIC32 part.
The series resistance and capacitance issues mentioned above are design problems, which shouldn't apply here. These are discussed in Microchip's documentation for designing PICKit compatibility into products. If the PICKit3 has been independently verified to work and the board is getting power, then the most likely problem is with the PIC32 part itself.
Gene Apperson Digilent
Mon, 04 Jul 2011 11:30:44 +0000
It is necessary to use a cable between the PICKit3 and the chipKIT board to make the connection, as the PICKit3 will physically interfere with the power connector or the USB connector when plugged in directly.
Or you can just plug the header in on the underside of the board -- the staggered pins hold it well without requiring soldering. Be sure to get pin 1 right.
Do you know a simple test to see if the cpu is still alive or not ?
If you don't see the heartbeat blink from the bootloader on d13 and you have not used the pickit3 to explicitly overwrite the bootloader, you might be in trouble.
Have you tried the standalone programmer application: http://www.microchip.com/forums/tm.aspx?m=554515&mpage=1#554515
That might narrow down if you have a software issue talking to the pickit3...
Note that if you are trying to load StickOS on a chipKIT, you don't need a pickit3 -- you can just load it using avrdude and the existing bootloader on the chipKIT. See: http://www.cpustick.com/bootloader.htm#cab
Mon, 04 Jul 2011 22:43:31 +0000
Hi and thank you for this info ;) But i found why it was not possible to communicate with the PIC32. the 3.3v regulator was dead and let the 5v go to the PIC. It was not hard to find out , i measured the voltage on some pins and everything was close to 5v. So i unsolder the 3.3v dead regulator and have give directly 3.3v to the board. The 5v is still ok for the usb/rs232 converter. But it seam that the cpu is dead. So then i just have to return to my old dev board. I hope for other user that the board shipped around are better tested than mine :shock:
Sat, 09 Jul 2011 02:15:06 +0000
I am also having the same problem. I bought a Uno32 and a Max32. I can program the Uno32 just fine. However my Max32 doesn't seem to talk to my PicKit 3. I just got the board so I would be shocked if the board is damaged.
I've contacted support and am awaiting for a response.
Tue, 12 Jul 2011 00:36:27 +0000
Ar Druid O, darthpic:
Did you guys ever figure out what was wrong with your Max32 boards?
Tue, 12 Jul 2011 01:23:46 +0000
In my case it was the mechanical connection. ("Force-fit" a header? Really? :roll: )
I soldered in a 6-pin header and used pre-made breadboard wires to connect to the picKit3. Works fine now.
Tue, 12 Jul 2011 01:37:25 +0000
Thanks for the response. I think my board is dead. It gets power but I can't get the PicKit 3 to work with it. I have ruled out my PicKit 3 being the problem because I can program other PIC32 boards.
I always get:
Target detected Failed to get Device ID Programming... Failed to program device
Wed, 27 Jul 2011 10:42:45 +0000
Sorry for the late answer , i'm just back from vacation ;)
On my board it was the 3v regulator. And for me it is the cause that the CPU is dead. As i said i have then remove this regulator and have give 3.3v to the PIC32 but it was dead. So now if you want test the 3v regulator without power the CPU , it dont know how you can proceed. Anyway , here it was 5v everywhere.
Good luck :D
Wed, 27 Jul 2011 13:18:19 +0000
I ended up RMA'ing my board. Digilent's support staff were the best I have ever had to deal with. They were extremely helpful and quick to respond.
My company will be ordering other products with them in the future.
Sun, 01 Jan 2012 01:19:16 +0000
Using a Max32 and PICkit3 with MPLABX, I set the project properties device and hardware tool to the correct values and compiled a small program with no problems.
Trying to debug, I get this error:
Target Device ID (0x4307053) does not match expected Device ID (0x4a04053)
The board came with a software that blinked the LEDs, and it worked fine.
The board usb is connected for power, and the PICkit3 is connected correctly with a short cable.
I have successfully used MPLABX and PICkit3 to program and debug a board with a PIC32MX220F032D. I am using ubuntu 10.04, but that should not matter.
Wed, 04 Jan 2012 17:01:35 +0000
Using a Max32 and PICkit3 with MPLABX, I set the project properties device and hardware tool to the correct values and compiled a small program with no problems. Trying to debug, I get this error: Target Device ID (0x4307053) does not match expected Device ID (0x4a04053) The board came with a software that blinked the LEDs, and it worked fine. The board usb is connected for power, and the PICkit3 is connected correctly with a short cable. I have successfully used MPLABX and PICkit3 to program and debug a board with a PIC32MX220F032D. I am using ubuntu 10.04, but that should not matter. Any ideas? g.
What's your target set too? Should be PIC32MX795F512L
Thu, 19 Jan 2012 16:51:41 +0000
I had that same problem and what i did was open my project in mplab, then connect the pickit3 to the usb, connect the MAX32 to another usb cable and when the computer was done veryfing the hardware i connected the pickit3 to the Max32 board.
According to what i have readed if the pickit3 doesnt see something connected the first time the boards are joined mplab doesnt recognize it.