A bit of help please

Created Sat, 21 Jan 2012 22:48:50 +0000 by omarm

omarm

Sat, 21 Jan 2012 22:48:50 +0000

Hi I'm new to the chipkit Max32. I've connected the Max32 to a laptop running Windows 7 64 bit and windows has installed 2.8.14 FTDI driver. I run Blink, but it only runs for 5 blinks and then resets. What's odd is if I leave the Serial Monitor open it seems OK ad continues to endlessly blink. The MPIDE is 20111221. Any idea how to stop it resetting itself? :?:

lloyddean

Sat, 21 Jan 2012 22:55:50 +0000

Is this an unmodified version of the example blink or have you modified it in any way?

If you've modified it try posting the modified version here.

Jacob Christ

Sun, 22 Jan 2012 00:49:39 +0000

Hi I'm new to the chipkit Max32. I've connected the Max32 to a laptop running Windows 7 64 bit and windows has installed 2.8.14 FTDI driver. I run Blink, but it only runs for 5 blinks and then resets. What's odd is if I leave the Serial Monitor open it seems OK ad continues to endlessly blink. The MPIDE is 20111221. Any idea how to stop it resetting itself? :?:

I believe in the Windows version of MPIDE unless the terminal is open the FTDI holds the board in reset. There is a cut trace on the board that can be severed is you want to disable this functionality.

This does not happen with MPIDE in Linux.

Jacob

les1943

Sun, 22 Jan 2012 10:08:41 +0000

I was thinking about cutting the rst trace , but then how will the bootloader get control to upload new code ? (my finger on the button [at the right time] I guess)

also.I have noted various thing will cause a reset, loading another MPIDE window, if any other usb port initializing takes place the FTDI will reset the board the Blink should run continually .( this is with XP and UNO32)

omarm

Sun, 22 Jan 2012 14:27:37 +0000

Thanks all. That's very useful. I was going to try a different COM Port, but it seems it's a facet of Windows and by the way Blink was unmodified.

Jacob Christ

Sun, 22 Jan 2012 17:07:07 +0000

I was thinking about cutting the rst trace , but then how will the bootloader get control to upload new code ? (my finger on the button [at the right time] I guess)

There is a jumper that can be installed once the trace is cut to re-establish the functionality.

Jacob

les1943

Sun, 22 Jan 2012 20:17:20 +0000

Thanks Jacob, I might install a switch its annoying when the board resets if i turn on the printer ......

rinka

Tue, 14 Aug 2012 17:50:44 +0000

Here's what worked for me.

I'm running Kubuntu on i5 (64bit). connecting to a MAX32

I first installed all the libraries rxtx-javalib, reinstalled avrdude

1. renamed avrdude to avrdude.old

2. linked /usr/bin/avrdude to this directory (see below) :~/bin/mpide-0023/hardware/tools$ ll total 2592 drwxr-xr-x 2 group name 4096 Aug 14 22:51 ./ drwxr-xr-x 5 group name 4096 Dec 22 2011 ../ lrwxrwxrwx 1 group name 16 Aug 14 22:51 avrdude -> /usr/bin/avrdude* -rw-r--r-- 1 group name 754889 Dec 22 2011 avrdude64 -rw-r--r-- 1 group name 541314 Dec 22 2011 avrdude.conf -rw-r--r-- 1 group name 528168 Dec 22 2011 avrdude.conf.0 -rwxr-xr-x 1 group name 268592 Dec 22 2011 avrdude.old* -rw-r--r-- 1 group name 541314 Dec 22 2011 brian-avrdude.conf

3. started mpide

4. set Tools >> Programmer >> w/ AVRISP mk II

5. set the board correctly.