AVR-Chat

On 4/27/10 8:21 PM, Jim Wagner wrote:
> Never used avrdude from the command line but I wonder if its not all a
> result of that first failure line = "command failed".
>
> Jim Wagner
> Oregon Research Electronics
>
> On Apr 27, 2010, at 7:08 PM, Brewski wrote:
>
>> Using an STK500 and an Olimex board on 3 different mega8515 chips I
>> get the following signature error, any ideas? Oh, a mega8535
>> programs perfectly on both the STK500 and the Olimex board. Of
>> course the the Olimex boards are different, each was make for a
>> specific chip, 8515 and 8535. This is on a Linux Ubuntu OS running
>> Make and Avrdude. The code compiles fine, it is when Avrdude tries
>> to program or erase the chip I get the error. This error was
>> received trying to erase the chip in the Linux terminal. Also, I
>> thought the -F option was to ignore an incorrect signature.
>>
>> $ avrdude -c stk500 -p atmega8515 -P /dev/ttyUSB0 -e -F -U
>> flash:w:sw-led.hex
>>
>> avrdude: stk500v2_command(): command failed
>> avrdude: stk500v2_recv(): checksum error
>> avrdude: stk500v2_program_enable(): bad STK600 connection status:
>> Unknown (0x64)
>> avrdude: initialization failed, rc=-1
>> avrdude: AVR device initialized and ready to accept instructions
>> avrdude: Device signature = 0x000000
>> avrdude: Yikes! Invalid device signature.
>> avrdude: Expected signature for ATMEGA8515 is 1E 93 06
>>
>> avrdude done. Thank you.

I looked up the chip types using avrdude and I see an ATMEGA8515 listed 
as m8515

ie, that should be:

avrdude -c stk500 -p m8515 -P /dev/ttyUSB0 -e -F -U flash:w:sw-led.hex
-- 
Clark Martin
Redwood City, CA, USA
Macintosh / Internet Consulting

"I'm a designated driver on the Information Super Highway"