Hi i have some problems trying to upload a sketch to a atmega 644.When I use ardunio 0023 and select "sanguino" under board It will upload fine.However when I use Ardunio 1.0.1 with the updated sanguino core files especially for 1.0.1 I get the following error :
avrdude: Yikes! invalid device signature
double check connections and try again or use-f to override
Ok I downloaded ardunio 1.0.3 then I extracted everything in the mighty-1284p-master to ardunio-1.0.3/hardware/ .Then added the following to the boards.txt located in the ardunio-1.0.3/hardware/mighty-1284p-master.
However when "Mighty 1284p 16MHz using Optiboot >> Mighty 644p 16MHz using Optiboot " is selected under boards and I try and upload a sketch I get the following error:
"unknown MCU 'atmega1284p >>atmega644p' specified (then a list of at mega's)
And a copy of the 644P bootloader code was placed into my C:\Documents and Settings\Primary Windows User\My Documents\Arduino\Arduino1\hardware\maniacbug-mighty-1284p\bootloaders\optiboot folder.
Yeah flak88, you need to fix the lines with comments in them:
mighty_opt.name=Mighty 1284p 16MHz using Optiboot >> Mighty 644p 16MHz using Optiboot
becomes:
mighty_opt.name=Mighty 644p 16MHz using Optiboot
mighty_opt.upload.maximum_size=130048 >> 63488?? with 2K bootloader
becomes
mighty_opt.upload.maximum_size=63488
mighty_opt.build.mcu=atmega1284p >> atmega644p
becomes
mighty_opt.build.mcu=atmega644p
or
mighty_opt.build.mcu=atmega644
depending on if you have a 'p chip or not
and point to the correct bootloader:
mighty_opt.bootloader.file=optiboot_atmega1284p.hex
Ok Ive made the changes and now im getting when I try and upload the following error "avrdude : stk500_getsync(): not in sync:resp=0x49".Tried mighty_opt.build.mcu=atmega644 and mighty_opt.build.mcu=atmega644p made no difference.
@pito yes I can confirm it does upload on 0023 arudino IDE so circuitry is fine but not any other version like the latest 1.0.3 for some reason.Ive tried pulling rst to gnd quickly then back to vcc via 10k resistor just before I click the upload button and still get error "avrdude : stk500_getsync(): not in sync:resp=0x49" .
flak88: @pito yes I can confirm it does upload on 0023 arudino IDE so circuitry is fine but not any other version like the latest 1.0.3 for some reason.Ive tried pulling rst to gnd quickly then back to vcc via 10k resistor just before I click the upload button and still get error "avrdude : stk500_getsync(): not in sync:resp=0x49" .
So what bootloader do you have burned into your 644 chip and what board.txt entry did you end up using?
Im not sure 100% which boot loader is on my 644 pretty sure its sanguino.
Well the IDE is expecting that the bootloader is designed to talk at 115200 baud rate which the older standard sanguino bootloader didn't. So either burn the new 644 optiboot bootloader onto the chip or edit that boards.txt entry for the baud rate your existing bootloader on the chip is using, whatever that baud rate is. You also may have to edit the mighty_opt.upload.maximum_size=63488 value as the value is based on the what is left over after you install the bootloader and the opitboot is smaller then older standard bootloaders.
Is it possible to burn a bootloader on a 644 by using a atmega 328 or does it need to be a programmer ?
Well most any 328P based arduino board running the arduinoISP sketch can be used as a 'programmer' to burn bootloaders onto target chips.
Also need to know if you have a 644 or a 644P chip as that might run into problems because of different chip signature bytes. Not sure what problems that might become or how to over come it.