Tue 12 Jan 2010 10:38:46 PM UTC, comment #1:
I'm afraid it's either a problem with your programmer,
or your ISP clock being too high (as someone already
suspected in the mikrocontroller.net forum). I ran your
test file on a genuine STK500v2 (not even using the most
recent firmware), and it programmed the EEPROM fine:
% ./avrdude -C avrdude.conf -p attiny85 -c stk500v2 -P /dev/cuad0 -B10 -U ee:w:/tmp/test.eep:r
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.01s
avrdude: Device signature = 0x1e930b
avrdude: reading input file "/tmp/test.eep"
avrdude: writing eeprom (512 bytes):
Writing | ################################################## | 100% 1.29s
avrdude: 512 bytes of eeprom written
avrdude: verifying eeprom memory against /tmp/test.eep:
avrdude: load data eeprom data from input file /tmp/test.eep:
avrdude: input file /tmp/test.eep contains 512 bytes
avrdude: reading on-chip eeprom data:
Reading | ################################################## | 100% 0.59s
avrdude: verifying ...
avrdude: 512 bytes of eeprom verified
avrdude: safemode: Fuses OK
avrdude done. Thank you.
This is with the SVN version of AVRDUDE although I doubt
it will make a difference to stock version 5.8 except for
the SVN version being faster since it uses paged writes.
Just noticed in your log:
Vtarget : 0.0 V
SCK period : 0.1 us
Whatever that means for your programmer... My STK500
reports:
Vtarget : 3.3 V
SCK period : 9.8 us
(I've been using option -B10 to be on the safe side, as
my ATtiny85 ran with the default 1 MHz clock.)
|