I am having the famous stk500_getSync() error when I try to upload a sketch.
avrdude: stk500_getsync(): not in sync: resp=0x30
avrdude: stk500_disable(): protocol error, expect=0x14, resp=0x51
It started happening after I put my seeeduino an Ethernet and Color LCD shields together. I bought the Shields from nuelectronics.com and they still working individually (with another seeeduino).
I tried to upload the bootloader again, as is suggested here in some other topics. However, it also didn't work. Avrdude can't connect to the board.
So, I think something was burned. (I don't have enough technical skill to find out).
The first question is: Can I use Nuelectronics Ethernet shield with the Color LCD Shield?
Second: Is there any other process that I could try besides the bootloader upload?
If you take away both shield can you send a sketch to the board (eg. the simple blink sketch)? the shields shouldnt be a problem unless they use the same pins and take more juice then the arduino can provide.
no, I can't upload the Blink sketch.
I guess the problem is not related to the COM port because I can plug another seeduino in the same cable and it works.
Yeah I'm pretty sure its you Atmega. You can buy a preloaded Atmega from a ton of places though. Good excuse to purchase a few more parts that you've been eyeing too.
I guess so.
The sad part is that Seeduino has the Atmega soldered to it. And even worse, I am not sure if I caused this malfunction due to the usage of Ethernet + LCD. I will study a little more, before trying it again with the other seeeduino.
hmm... yeah that sucks. do you remember the previous program you had on there that worked? If you had something liek a blink program on before, you could hook up a voltmeter to pin 13 on the atmega and see if it blinks it. you could trouble shoot like that and see if the atmega is really the problem
as for a malfunction to be cause by the combination, i really don't know what the issue could be. are the shields badly soldered?, im wondering if it had a part to play in shorting you board somehow and that caused a problem for your micro.
