XaroRSA wrote:

Hold in reset button, press upload, keep reset button pressed until you get "binaries" message, release reset button.
Wolaha

I believe those are the steps for uploading firmware not burning the bootloader.

I get no "binaries" message when attempting to burn the bootloader. 

I do get the "binaries" message when trying to upload the firmware but, again, there is no bootloader on the chip....

What sort of AVR programmer are you using to burn the bootloader? If you use TinyISP we might be able to help.

Hold in reset button, press upload, keep reset button pressed until you get "binaries" message, release reset button.
Wolaha

I believe those are the steps for uploading firmware not burning the bootloader.

I get no "binaries" message when attempting to burn the bootloader. 

I do get the "binaries" message when trying to upload the firmware but, again, there is no bootloader on the chip....

Diecrusher, I have read that there are various fuse settings on the microcontroller that must match the programmer. In an Uno, the MC uses an external oscillator, but being programmed by itself it will use its internal oscillator and need a different setting.

Any suggestions what to try? 

Like I said, I am a complete Arduino novice so besides my Google searchs any hand holding would be appreciated!

Diecrusher:
Have you tried another USB cable? I had some really strange problems with firmware upgrade earlier because of a bad USB cable. After replacing it, everything worked like a charm..

Well, while I wait for the replacement ATMega644p chip w/ a bootloader on it to be sent from SD, I thought that I might be adventurous and learn to bootload the chip myself.

I picked up a Arduino Uno and followed various online guides to using it with a breadboard setup as a AVRprogrammer.

Funny thing is I get the same errors as when I tried upgrading the firmware to that chip with the SD's Sanguino.

Perhaps the chip is just 'Bricked'.

There is an experimental Marlin branch for Arduino 1.0.1, but we are still forked from the main branch which uses 022. If the wrong Arduino IDE was being used, it would not compile and he wouldn't get as far as that error.

ah, I thought it was a seperate entity. cheers

i assume ver 22 (however it was numbered) is still the correct version to use, no chance a later version is being used now ?

I just put the original chip that I recieved the SD with and Pronterfaces starts right up and I am printing as I type this... no problem.

Just couldn't get the new chip working nor could I write firmware to it.  Maybe their is something wrong with my Sanguino board?  I am at a total loss.

I will contact Solidoodle in a couple of days..... I know they have more important matters to deal with (Sandy).... I hope they are okay.

Not sure if there is a way to test for a bootloader besides the upload working. Have you tried googling that?

I just recieved a new chip from SD today.  It is installed correctly, no damaged pins, orientated the right way, etc.

When I try to update I get the same error as before.

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

I've tried different usb port, different baud, OSX on MacBook Pro, Win7 on MacBook Pro, Winxp on Dell D600.....same result.  I tried all the reset button timing tricks too to no avail.

So.... I figured that maybe the latest firmware was already installed by SD.  I fire up Pronterface but the machine won't connect and I just hear funny whirring noises inside the machine so I figure that perhaps nothing is installed on the chip.

I go back to the original chip sent with the SD and it connects just fine but still can't update the firmware.

What gives?????