have a diecimila and got the same thing
just got 0016
loop feedback does not work
i am just doing Blink
i got with verbose mode on:

Binary sketch size: 896 bytes (of a 14336 byte maximum)


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


        Using Port            : \\.\COM4
        Using Programmer      : stk500v1
        Overriding Baud Rate  : 19200
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.


I Need Help!  

hey guys, i just saw this post come up about the mega... i don't really know what it might be, but the one i have at home works perfectly? i have a vista laptop that pretty much never worked (for some reason the driver crashes my computer every once in a while when it downloads, but that's with the diecimila and duemilanove too), so i always do programming on my xp desktop.

sadly i'm still at work but i'm going to run home as soon as i can to see if i can help. in the meantime i just emailed chris too i think he's home, and maybe he can see what's up?

hmmmm....

matt

Hi... i just tested 6 of the new Megas in my book case and none of them will program with Arduino 15 or 16.
i'm going to test the rest and see if i can figure out why these Arduinos aren't working...

Code:

I just took out my AVR ISPMKII and i will test the fuse bits on the processor to see if they are different from my working Megas...  

Maybe they missed the step to burn the bootloader  

Why don't you try and use your burner to try and reload the bootloader from the IDE.

Lefty

well... it isn't that either...

I just compared the working .hex with the other .hex
the boots look identical



I also tried to use the known good .hex on the other broken Mega... but as expected it did nothing...

next i'm taking out my scope and giving some tests to the serial signals going into the Arduino...

I have a hunch that this is some kind of hardware issue...

yay!!!

i got it!

all the arduinos had an incorrect cap placed on them...



so i looked at the reset pulses on both sides of this capacitor to see if it was charging properly when the reset was sent from the ftdi chip...



this was in fact the case...
the ftdi chip was outputing the correct signal, yet the arduino wasn't being reset...

so i replaced it with a 100nF capacitor that i found lying around from the touchshields i built...

the only problem is that the 100nF i used was 0402 surface mount technology... but hey



and...

program!

and fixed

if you bought an Arduino from my website, give me a call on my cell phone (860  930   6480) or shoot me an e-mail ( mike.gionfriddo@gmail.com ) and i will mail you out a fixed MEGA as soon as possible...

sorry for the delay...

Good troubleshooting, thanks for sharing your experiance.

Looking back now that we know the root cause, a test using the manual reset button while uploading a sketch would have worked and helped isolate the problem quicker and with less steps? Sorry, I was a hardware troubleshooter before retirement and can't help myself, I always tried to keep a lessons learned list on equipment I had to support.  

Lefty