error uploading in Arduino

[Gowan]

I tried compiling and uploading the two Blink sketches and the Button
sketch.
All failed with this message:
"
avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51
"
I'm not crying "wolf" here.
Any help is appreciated.

[Rugged Circuits]

Can you specify your hardware and software configuration? Is this a
Gator board or an Arduino variant? Which Arduino software release are
you using?

[Gowan]

I'm using a Gator board. The Arduino software is 0018-gator.

[Rugged Circuits]

On Mon, Nov 8, 2010 at 1:51 PM, Gowan <peters...@telus.net> wrote:
> I'm using a Gator board. The Arduino software is 0018-gator.

Did you set the preferences to enable the reset dialog? This is
described on our Arduino support page:

http://ruggedcircuits.com/html/arduino.html

1. Start the Arduino program then select File->Preferences. At the
bottom of the Preferences dialog you will see a pathname that points
to a file named ‘preferences.txt’. Make a note of the full pathname
for this file.
2. To edit this file, you must first CLOSE the Arduino program,
otherwise any changes you make to the preferences file will be lost,
as the Arduino program overwrites this file when it exits.
3. After you have closed the Arduino program, open the preferences
file in a text editor and add the following line at the bottom:

upload.reset_dialog=true

The ‘preferences.txt’ file will not exist if the Arduino program has
never been run. In this case, it will be created automatically the
first time the program runs and the ‘upload.reset_dialog’ option will
be set to ‘true’ by default.

Since the Gator does not auto-reset when the serial port is opened,
you have to physically press the reset button right before the upload
begins. The reset dialog helps with this by letting you know when you
have to press the reset button.

[Gowan]

Yes, I made sure that line was in the preferences file. The reset
dialog box has come up each time. After I press the reset button, the
light blinks 2-3 times, then comes on steadily for 3-4 seconds and
then goes off. I press the button in the dialog box and after 30-60
seconds, the error messages appear.
Thanks

[Rugged Circuits]

It sounds like you are not dismissing the dialog box quickly enough.
As soon as the LED starts blinking you have to dismiss the dialog box.
Once the LED stops blinking the Gator is no longer looking for a new
program to be downloaded.

[Gowan]

I tried quite a few different combinations of recompiling,
reloading, closing and starting again.
Also many different delays between pressing the reset button and
dismissing the dialog box.
To no avail.
Here's what happens:
open Button, a new console opens with Button loaded.
compile
upload, console displays "uploading to i/o board...", wait 120
seconds.
dialog box opens. press reset, dismiss dialog, console displays
"uploading to i/o board...", wait 25 seconds.
console diplays error msgs detailed above.
The messages don't provide a hint eh?
Thanks

[Rugged Circuits]

On Nov 9, 9:38 am, Gowan <peterstew...@telus.net> wrote:
> Here's what happens:
>      open Button, a new console opens with Button loaded.
>      compile
>      upload, console displays "uploading to i/o board...", wait 120
> seconds.
>      dialog box opens.

That's unusual. There is no reason to have to wait 120 seconds for the
dialog box to open. Does this happen with the non-Gator Arduino
software too? I'm wondering if you should try reinstalling the Arduino
software.

> press reset, dismiss dialog, console displays
> "uploading to i/o board...",  wait 25 seconds.
>      console diplays error msgs detailed above.
> The messages don't provide a hint eh?
> Thanks

Try pressing the SHIFT button and holding it down when you click on
the Compile/Verify button in the toolbar. That should print more
diagnostic messages as it's compiling.

[Gowan]

There follows the diagnostic message. I pressed 'shift' before the
original upload, and then again when I pressed reset and dismissed the
msbbox.
<<
Binary sketch size: 968 bytes (of a 30720 byte maximum)
C:\Program Files\Arduino\arduino-0018\hardware/tools/avr/bin/avrdude -
CC:\Program Files\Arduino\arduino-0018\hardware/tools/avr/etc/
avrdude.conf -v -v -v -v -patmega324p -cstk500v1 -P\\.\COM1 -b38400 -D
-Uflash:w:C:\Users\Peter\AppData\Local\Temp
\build6903266696002383508.tmp\Blink.cpp.hex:i


avrdude: Version 5.4-arduino, compiled on Oct 11 2007 at 19:12:32
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/

System wide configuration file is "C:\Program Files\Arduino
\arduino-0018\hardware/tools/avr/etc/avrdude.conf"

Using Port : \\.\COM1
Using Programmer : stk500v1
Overriding Baud Rate : 38400
avrdude: ser_open(): setting dtr
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Send: 0 [30] [20]
avrdude: Recv:

avrdude: stk500_getsync(): not in sync: resp=0x00

avrdude: Send: Q [51] [20]
avrdude: Recv:

avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

avrdude done. Thank you.
>>

[Rugged Circuits]

On Nov 9, 6:26 pm, Gowan <peterstew...@telus.net> wrote:
> There follows the diagnostic message. I pressed 'shift' before the
> original upload, and then again when I pressed reset and dismissed the
> msbbox.
> <<
> Binary sketch size: 968 bytes (of a 30720 byte maximum)
> C:\Program Files\Arduino\arduino-0018\hardware/tools/avr/bin/avrdude -
> CC:\Program Files\Arduino\arduino-0018\hardware/tools/avr/etc/
> avrdude.conf -v -v -v -v -patmega324p -cstk500v1 -P\\.\COM1 -b38400 -D
> -Uflash:w:C:\Users\Peter\AppData\Local\Temp
> \build6903266696002383508.tmp\Blink.cpp.hex:i

OK, so you've got a hex file out of it:

C:\Users\Peter\AppData\Local\Temp\build6903266696002383508.tmp
\Blink.cpp.hex

Try uploading this hex file to the Gator using the Gator GUI rather
than through the Arduino GUI.

If that still doesn't work you may have to re-flash the bootloader on
the Gator. This can be done through the Gator GUI Setup tab.

[Gowan]

There was no \Blink.cpp.hex at that location. I could find no
Blink.hex or Blink.*hex at all.
I reflashed it all with the Gator GUI Setup tab.
The first two checked out fine. But the last:
install board test went fine, left the lcd blinking
run board test failed with this report:
<<
FLASH integrity test passed
All lines pulled-up: 00FFFFFF
*** Port A pin 0 stuck low
*** Port A pin 1 stuck low
*** Port A pin 2 stuck low
*** Port A pin 3 stuck low
*** Port A pin 4 stuck low
*** Port A pin 5 stuck low
*** Port A pin 6 stuck low
*** Port A pin 7 stuck low
PORTA(0) pulled low: FEFFFFFF
PORTA(1) pulled low: FDFFFFFD
PORTA(2) pulled low: FBFFFFFD
PORTA(3) pulled low: F7FFFFFD
PORTA(4) pulled low: EFFFFFFD
PORTA(5) pulled low: DFFFFFFF
PORTA(6) pulled low: BFFFFFFD
PORTA(7) pulled low: 7FFFFFFD
PORTB(0) pulled low: FFFEFFFD
PORTB(1) pulled low: FFFDFFFF
PORTB(2) pulled low: FFFBFFFD
PORTB(3) pulled low: FFF7FFFD
PORTB(4) pulled low: FFEFFFFF
PORTB(5) pulled low: FFDFFFFF
PORTB(6) pulled low: FFBFFFFD
PORTB(7) pulled low: FF7FFFFD
PORTC(0) pulled low: FFFFFEFD
PORTC(1) pulled low: FFFFFDFD
PORTC(2) pulled low: FFFFFBFD
PORTC(3) pulled low: FFFFF7FD
PORTC(4) pulled low: FFFFEFFD
PORTC(5) pulled low: FFFFDFFD
PORTC(6) pulled low: FFFFBFFD
PORTD(2) pulled low: FFFFFFF9
PORTD(3) pulled low: FFFFFFF5
PORTD(4) pulled low: FFFFFFEF
PORTD(5) pulled low: FFFFFFDD
PORTD(6) pulled low: FFFFFFBD
PORTD(7) pulled low: FFFFFF7D
All lines low: 0000C003
PORTA(0) driven high: 0100C003
PORTA(1) driven high: 0200C003
PORTA(2) driven high: 0400C001
PORTA(3) driven high: 0800C001
PORTA(4) driven high: 1000C003
PORTA(5) driven high: 2000C001
PORTA(6) driven high: 4000C001
PORTA(7) driven high: 8000C003
PORTB(0) driven high: 0001C001
PORTB(1) driven high: 0002C003
PORTB(2) driven high: 0004C001
PORTB(3) driven high: 0008C001
PORTB(4) driven high: 0010C003
PORTB(5) driven high: 0020C003
PORTB(6) driven high: 0040C003
PORTB(7) driven high: 0080C001
PORTC(0) driven high: 0000C103
PORTC(1) driven high: 0000C201
PORTC(2) driven high: 0000C403
PORTC(3) driven high: 0000C803
PORTC(4) driven high: 0000D001
PORTC(5) driven high: 0000E001
PORTC(6) driven high: 0000C003
PORTD(2) driven high: 0000C005
PORTD(3) driven high: 0000C00B
PORTD(4) driven high: 0000C013
PORTD(5) driven high: 0000C023
PORTD(6) driven high: 0000C041
PORTD(7) driven high: 0000C081
>>

[Rugged Circuits]

On Nov 10, 12:44 pm, Gowan <peterstew...@telus.net> wrote:
> There was no \Blink.cpp.hex at that location. I could find no
> Blink.hex or Blink.*hex at all.

It looks like the Arduino GUI deletes those files once it is done with
them.

> I reflashed it all with the Gator GUI Setup tab.
> The first two checked out fine. But the last:
>    install board test went fine, left the lcd blinking
>    run board test failed with this report:

That's fine...the board test report is not significant. You can
communicate with the Gator and if you installed the test program that
means the bootloader is working. It looks like the problem is with the
Arduino GUI then.

I'm afraid there's not much we can suggest for fixing this program
other than trying the non-Gator version (you'll simply have to press
the Gator reset button at the right time), trying a different USB
port, rebooting the computer (of course), trying it on a different
computer, etc.

[Gowan]

OK, thanks for the advice.

[Matt]

Wondering if you figured out how to fix this problem as i am
experiencing the same or very similar.
After installing the gator-arduino-0018 software and hooking up the
gator board, i attempted to load the Blink example and, after pressing
reset, got the same error message except with a different resp value:

avrdude: stk500_getsync(): not in sync: resp=0x30

avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

Matt

[Gowan]

I stopped working on the Arduino connection at this point. I felt that
I'd received a lot of good advice.

>I'm afraid there's not much we can suggest for fixing this program
>other than trying the non-Gator version (you'll simply have to press
>the Gator reset button at the right time), trying a different USB
>port, rebooting the computer (of course), trying it on a different
>computer, etc.

To procede would be to invite more frustration.
However, to program is to be frustrated!
I went on to get the UART0 working, coding in c.