I just got an arduino mega and can't upload my program to it. When I hit upload the computer thinks for a minute, displays the binary sketch size and limit (size is well under the limit) and after it thinks some I get the following error
avrdude: stk500_getsync(): not in sync: resp=0x30
avrdude: stk500_disable(): protocol error, expect 0x14, resp=0x51
my operating system is Windows Vista, board, arduino mega, first time trying to upload
any help would be greatly appreciated,
thanks
Do you have the correct board selected?
Do you have the correct serial port selected?
Have you tried a different USB cable?
What steps have you taken to troubleshoot the problem?
Judging by the amount of "I can't upload"-threads that have popped up lately, I think that either (or even both) of these facts may be true:
Which is it and why?
BTW, didn't we have [sticky] threads with most of the common errors and fixes in the two 'troubleshooting' sections ?
Have you installed the correct/newest/any fdti drivers?
BTW, didn't we have [sticky] threads with most of the common errors and fixes in the two 'troubleshooting' sections ?
We most certainly should at any rate :(. I see 3-5 of these posts every week (if not more!).
We most certainly should at any rate . I see 3-5 of these posts every week (if not more!).
It's been that way sense I joined this site. It reflects that fact that the Arduino set-up is not truly 'plug and play'.
Now 99% of the time it's not the Arduino board's fault, as there is nothing to set-up on the board side, it is a plug and play part. However on the software side that is not the case.
One has to install the Arduino IDE software correctly, then load and activate the FTDI drivers correctly and finally select the proper board type and comm port number in the IDE. While this might seem trivial to us now experienced with running a Arduino, there are lots of steps a newcomer can trip up on.
What would help possibly would be a screen shot step by step installation and set-up document, or possibly a video. OF course it would have to be done three different ways depending on host platform being used.
So while there are many problems reported here from newcomers, I don't have a good feel for the percentage of Arduino users having problems at first, there has been a zillion Arduinos sold I bet, so the users having initial setup problems may be very small.
Lefty
OF course it would have to be done three different ways depending on host platform being used.
That would seem to be Windows, Mac, and Linux.
But there's Windows XP, Windows Vista, and Windows 7. There's 32 bit and 64 bit.
Then, there's several versions of the Mac OS. Some seem more Arduino friendly than others.
And, there's a zillion variations of Linux - Ubuntu, Kubuntu, FreeBSD, RedHat, Debian, Gentoo, openSuse, etc.. 32 bit and 64 bit.
Looks like more than 3...
-Yes I selected the arduino mega
-Yes I've got the correct serial port (only have one option)
-Only have one USB cable but I did try other ports
-I've read through all the basic troubleshooting from the FAQ and its all inline...only security i have is the free norton that came with the computer which i have yet to figure out how to disable
-the IDE was installed less than 4 days ago so it should be up to date
....scratch that, when i rebooted it gave me a second serial port option and it worked...sorry for the trouble
A sharp left off track ...
Then, there's several versions of the Mac OS. Some seem more Arduino friendly than others.
I'm not sure what this refers to. I've had the Arduino IDE on three different versions of Mac OS X, and I can't remember any differences.
I think only showing 1 version of Mac OS X would be acceptable 
Of course, that only reduces the number by 2 
There are definite differences between versions of Windows, but does it really show up at the level of 32-bit and 64-bit?
In my experience, it's installing the FTDI driver which causes all of the problems. Schools can't get it working on their 'thin client' networks, and several people have had problems installing on laptops.
I've also had people in Arduino workshops who were developers building their own Linux kernel, and had removed USB serial support.
mbed have the entire development environment on the web. I prefer the current Arduino approach to development (I like to be able to work when out of range of the Internet), but maybe a web hosted IDE might be worth considering to allow folks to get started without any installation.
A web-hosted approach works for the mbed because it doesn't need any device drivers. It looks like a flash drive to the host PC, so it is easy for the user to save the binary program file straight onto the mbed.
Their are a bunch of USB classes that could be used, it doesn't need to be flash drive. For example, my wireless router lets me upload updates to its firmware directly from my web browser.
GB-)
I'm not sure what this refers to. I've had the Arduino IDE on three different versions of Mac OS X, and I can't remember any differences.
Yes, but there are more versions of Mac than Leopard! Think of Tiger, etc..
but does it really show up at the level of 32-bit and 64-bit?
Absolutely. There are many programs that simply refuse to run on a 64-bit system. That number is decreasing daily due to the growing number of 64-bit users, but it's a developing hazard.
It's somewhat frightening that a windows user expects his machine to run properly without rebooting after installing a new driver. Don't get me wrong, it should be that way but I thought by now simply everybody knew that you have to reboot it. I may be wrong, but doesn't the FTDI installer kindly asks for a reboot?
Anyhow, we should have another [sticky] post concerning 'how to correctly ask for help'.
Yes, but there are more versions of Mac than Leopard! Think of Tiger, etc..
I am referring to 10.3, 10.4 and 10.5 on PowerPC and 10.4, 10.5 on Intel MacBook.
I don't believe I know anyone who thinks that the minor version number represents an OS version, so your comment is educational. Thank you. I'll try to be clearer in the future.
So, I repeat, I do not remember any differences installing the Arduino IDE, and I think one version of instructions would be sufficient for Mac OS X.
Absolutely. There are many programs that simply refuse to run on a 64-bit system. That number is decreasing daily due to the growing number of 64-bit users, but it's a developing hazard.
I don't think we are discussing 'many programs ...'.
I believe we were discussing installing the Arduino IDE and FTDI driver. Are you saying that the installation instructions for the 32-bit and 64-bit implementation of the same version of Windows varies?
HTH
GB
I seem to recall Grumpy_Mike mentioning something not working on one version of the Mac OS that used to work on a previous version. I don't have a Mac, so I didn't pay much attention to the particulars. Grump_Mike is a regular poster, and active user, so if he says something doesn't work on some version of Mac, I assume he knows what he's talking about.
Of course, it could be my memory that is faulty.
As for 32 bit vs. 64 bit, there have been a lot of posts in the last 6 months where someone says that such and such doesn't work on some version of windows, and someone else says that it does, and the difference between the system that failed and the one that worked was 32 bits.
If there are to be 3 videos/pages, then the 3 videos/pages need to make it clear that there are (potential) differences between the user's actual system and the system being used to demonstrate/develop the process.
That was my only real point in posting.
I don't think we are discussing 'many programs ...'.
I believe we were discussing installing the Arduino IDE and FTDI driver. Are you saying that the installation instructions for the 32-bit and 64-bit implementation of the same version of Windows varies?
I'm saying that installers have to work differently on 64-bit systems. This means the IDE has to be configured to work on 64-bit systems (which I have no idea if it is).
It would logically follow that yes, I would not be surprised at all if the installation instructions would have to vary some for 32-bit and 64-bit.
It's somewhat frightening that a windows user expects his machine to run properly without rebooting after installing a new driver.
I don't expect to reboot after installing a driver. Windows operating systems have supported dynamically loading / unloading kernel drivers since NT 4.0. The hardware vendors have had a few years to get their installs working correctly.
Don't get me wrong, it should be that way but I thought by now simply everybody knew that you have to reboot it.
The only case that should require rebooting is: old driver needs to be replaced and is currently "in use".
I may be wrong, but doesn't the FTDI installer kindly asks for a reboot?
The install didn't bother me to reboot.
Anyhow, we should have another [sticky] post concerning 'how to correctly ask for help'.
That would be nice. And it definately should include "reboot and try again"!