Welcome! Log In Create A New Profile

Advanced

burning bootloader

Posted by TonyBert 
burning bootloader
January 04, 2012 03:24PM
I've been trying to burn the bootloader on a new 1.3a board without success!

keep getting the following error messages

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

I'm using a Pololu USB AVR programmer (with fresh install and driver updates) as an ISP and it seems to be functioning correctly, green power light on and yellow LED indicating communication.

I've connected pin 1 of the programmer to the MISO pin on the sanguino board,
connected 12v power to the power connection and the power LED lit and stayed on,
tried with and without Pololu drivers installed,
using the atmega 644P-20 chip
Arduino 0018 and 1.0 versions with the respective libraries (data files?)
using an I7 win 7 64 bit system to attempt all this, even tried a winXP machine without any success

we did try to burn the bootloader with the atmega chip in backwards but don't know if that blew the chip or not, but5 still got the same error codes.

the autoreset jumper is shorted, tried with and without the shorting block, and holding in the reset switch in

Thanks for the help

Tony
Re: burning bootloader
January 05, 2012 10:46PM
Did you change the following entry in the arduino preferences.txt (for 0023 and below)? In Arduino 1.0 you can select your programmer in the menus.

upload.using=bootloader
to
upload.using=avrispv2

Make sure to edit with Arduino closed and change back to "bootloader" to upload using USB.

Edited 2 time(s). Last edit at 01/05/2012 11:16PM by royco.
Re: burning bootloader
January 06, 2012 02:29PM
I edited the file, saved, and the changes had no effect, still the same results
Re: burning bootloader
January 06, 2012 05:43PM
went with AVRDUDE in a DOS command box and used the following command from the installed directory

AVRDUDE -p m644p -P com7 -C avrispv2 -b 4800 -e -U flash:w:ATmegaBoot_644p.hex

avrdude would identify the chip as 0x1e960a
erase the chip
read the input file
auto detect the input file as Intel Hex
write flash (65382 bytes
writing 97% and then receive message() : timeout

it will of thru a series of writing 1% more with each series of timeouts

then AVRDUDE will read the memory 1% at a time with a series of timeouts

Something seems to be off ! blown chip? tried a new chip with the same results

The red led on the Pololu ISP is constantly lit which indicates the last attempt at burning resulted in an error, I tried 2 different chips with the same result.

all of the solder points look good and have been re-flowed

I seem to be getting closer but no luck yet.

anyone have any ideas?

Thanks

Tony
Re: burning bootloader
January 07, 2012 10:57PM
Success at last!!

I was able to reset the fuses successfully, but the bootloader still failed!!

After multiple failures attempting to copy the bootloader and having the bootloader upload time out at 97%, it seemed like either the bootloader file was corrupted or there was a size problem (bootloader to big for chip) or programmer problem.

Reviewing the Polo manual revealed a firmware upgrade was available and needed if the chips were larger then 256K and increasing the timeout period, but since we're only writing 65k it did not seem to be required but I didn't seem to have anything to loose by upgrading the Polo firmware.

After reflashing the Polo ISP firmware to V1.06, the bootloader flashed with no problem.

I also found it easier to write a batch file and run the batch file instead of manually typing in the the AVRDUDE commands everytime.

Tony
Sorry, only registered users may post in this forum.

Click here to login