Hi guys,

 

I have been working on an Arudpilot project for quite some time now. After a lot of testing, and the odd crash landing into the snow and elements, I thought it would be a good idea to get some new hardware. I believe the original hardware is beginning to fail... the leds are not solid, but often blink slightly as though connections are not good.

 

I just ordered an all new arduino 328 board, a new sheild kit, and a new gps, soldered it all together and tried to load code, but got the following error message.

 

Binary sketch size: 23160 bytes (of a 30720 byte maximum)

avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

 

I can still upload teh code onto my old board no problem, so I assume the problem must be something with my new hardware?

 

Thanks for any advice in advance!!

 

Jeff

Tags: ardupilot, code, problem, upload

Views: 17

Reply to This

Replies to This Discussion

Jeff,

What USB to serial adapter are you using: Sparkfun or Adafruit/DIY Drones Store?

Regards,
TCIII
I am using the DIY Drones FTDI cable
And maybe this is obvious, but you did select "Duemilanove or Nano w/ ATMega328" under Tools->Board in your Arduino IDE. Right?

Tom
Yes the board selection is correct, and so is the COM port selection
Have you been through all the debugging tips here?

Also, ensure you're using the latest Arduino (18)
Hey Chris,

I have gone through all of your de-bugging tips... I will explain exactly what is going on:

Last week I ordered two new ATMega328 boards (from sparkfun) and two new shields (blue, new version from DIY)

I can upload code onto my original board (ATMega328 bought in January) no problem.

I CAN NOT upload code onto EITHER of the new boards, I get the following error message:

Binary sketch size: 23160 bytes (of a 30720 byte maximum)

avrdude: stk500_getsync(): not in sync: resp=0x00
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51

SO... as your tips suggested, I downloaded arduino, the drivers, the code, etc onto a new computer, and exactly the same thing happens (can upload code onto original board, but get identical error messages when trying to upload to BOTH the new boards).

While troubleshooting, I noticed some un-expected differences between THE TWO NEW boards:
-when powered on, one board only shows the red power LED, the other shows red power LED AND intermittent flashing from the blue and yellow LEDs
-When only the FDTI is plugged in with no external power ( I know you cant upload code like this) one new board will show solid dim power LED, and the other new board only shows dim power LED when contact is initiallly made to the FDTI cable

Any ideas would be greatly appreciated!!!
oh and yes I am using arduino 18
It sounds like you got a bum batch of boards. The flashing sequence of LEDs us a led test program loaded at the factory. Both boards should have had it. And it sounds like they may not have been loaded with the bootloader.

This is really a Sparkfun thing but if you'd like me to check out your boards you can send them to me. Just PM me..
After reading many of the arduino forums, I was able to get the board with the flashing lock and stat lights uploaded. I ended up holding the reset button until arduino said "binary file......" then let go of the reset button (on the arduino board, not the sheild) and it was able to upload. Have you heard of this working before?

With the other board that did not display flashing lock and stat lights is still not working and I am going to try and send it back to sparkfun to get a new one.

What are the LEDs supposed to do upon inital power up?
If you have to manually reset that usually means that you don't have the "Set RTS on close" box checked in your Com options. All this is described in the manual here. Can you double check that?

When you first get the board from the factory the LEDs should flash in sequence (it's just an LED test program). Once you program it for the first time, the regular ArduPilot LED behavior takes over. Again, all this is described in the manual here.
Alright, that all makes sense, except that ever since I loaded the 2.5.4 I have had no stat light blinking, yet the system seems to be working???
Stat light behavior changed from 2.4 to 2.5. I'll have to update that table...

RSS

Contests

Season Two of the Trust Time Trial (T3) Contest has now begun. The third round was a reliablilty/aerial photography round for both planes and copters, which is now closed. Stay tuned for the next round, beginning soon.

A list of all T3 contests is here

 

© 2012   Created by Chris Anderson.

Badges  |  Report an Issue  |  Terms of Service