chipKIT® Development Platform

Inspired by Arduino™

can't program Max32 with MPIDE release mpide-0023-windows-20

Created Fri, 05 Oct 2012 18:55:03 +0000 by DandyDon


Fri, 05 Oct 2012 18:55:03 +0000

Hello, all!

I need some help, please! I can't seem to get my Max32 chipKIT board programmed w/ the simple Blink sketch...

I open MPIDE & select the Max32 board, using serial port COM3.

I connected the board to my laptop thru the USB cable, & the laptop said the drivers installed properly, but when I try to upload the sketch to the board I get error the messages:

avrdude: stk500v2_getsync(): can't communicate with device: resp=0x01 avrdude: stk500v2_command(): unknown status 0xc8 avrdude: stk500v2_command(): unknown status 0xc8 avrdude: stk500v2_program_enable(): cannot get connection status avrdude: initialization failed, rc=-1 Double check connections and try again, or use -F to override this check.

avrdude: stk500v2_command(): unknown status 0x01 avrdude: stk500v2_disable(): failed to leave programming mode

Any suggestions?


Fri, 05 Oct 2012 19:18:13 +0000

To me it sounds like it's trying to talk to a hardware serial port rather than your MAX32.

If you disconnect the MAX32, does the COM3 in the Serial Port menu go away (thus indicating that, in fact COM3 is the UNO32)?



Fri, 05 Oct 2012 20:22:18 +0000

Thanks for the response, Brian!

When I plug the Max32 chipKIT board into the USB cable & look at the Device Manager, the board comes up as a USB Serial Port, but there are no drivers associated with it. When I try searching for a driver, Windows can't find one... In Windows Explorer under the MPIDE installation folder, I can see a folder labeled FTDI USB Drivers but it still won't work!

I have a Microchip PICkit 3 & installed a header on the Max32 board for connecting it up. My laptop sees the PICkit 3 in MPLAB X, but I can't get the programmer to power the board, even though I check the box for that in the project options. When I try programming the board using MPLAB X it get an error saying no target device detected...


Fri, 05 Oct 2012 20:36:59 +0000

Hmm. So it's clearly a driver thing.

The MAX32 uses an FTDI USB to serial chip to convert the USB signal from the computer to async serial that talks to the PIC32. So you need to find a way to force Windows to accept the proper driver for the FTDI chip. One thing to try - go to [url][/url] and try installing the latest drivers for your particular flavor of Windows, then rebooting, then put the MAX32 on a different USB port on the PC (to force a driver update).

Unless you want to program bare-metal C in MPLAB, there isn't a good use for the PICKit3 connected to the MAX32. There is a serial bootloader that's programmed on the MAX32 at the factory, and if you erase that, the board will no longer work under MPIDE until you re-program the serial bootloader.



Tue, 09 Oct 2012 17:46:22 +0000

Thanks again, Brian!

I went to FTDI's site & got the newest drivers. That fixed it! I can see a new COM port & talk to the board...

U-da Man!