AVR-Chat

I have avrdude 5.5 and I'm pleased as can be with it, until now.

I am using the avr libc EEPROM routines and setting the EEPROM memory up 
properly to start with data in the EEPROM.  I've confirmed that the eep 
file is fine.  When I try to program my TINY2313 nothing after byte 3 
gets properly programmed in the EEPROM.  Sometimes it says everything is 
fine on the read back, but it isn't and sometimes avrdude tells me that 
the third byte doesn't verify.

I've Googled for this but found no definitive answer, I have not visited 
the avrdude site yet to search the bug data base.

Has anyone seen this before and solved it?  Is there a later version of 
avrdude that fixes the problem?  Am I simply doing something wrong?

thanks,
DLC
-- 
-------------------------------------------------
Dennis Clark          TTT Enterprises
www.techtoystoday.com
-------------------------------------------------

> Has anyone seen this before and solved it? Is there a later version of
> avrdude that fixes the problem? Am I simply doing something wrong?

Have you tried a different part?  We program a lot of Tiny2313 that
use section of the EEPROM, have not had any problems with AVRDude
doing it.



-- 
http://www.wearablesmartsensors.com/
http://www.softwaresafety.net/
http://www.designer-iii.com/
http://www.unusualresearch.com/

The EEPROM works fine - I can write and read it in a program, avrdude 
just won't write it during programming.  Maybe a timing setting in 
avrdude can correct that?

DLC

Bob Paddock wrote:
>> Has anyone seen this before and solved it? Is there a later version of
>> avrdude that fixes the problem? Am I simply doing something wrong?
> 
> Have you tried a different part?  We program a lot of Tiny2313 that
> use section of the EEPROM, have not had any problems with AVRDude
> doing it.
> 
> 
> 

-- 
Question with boldness even the existence of a God;
because, if there be one, he must more approve of the
homage of reason, than that of blind-folded fear.
Thomas Jefferson
-------------------------------------------------
Dennis Clark          TTT Enterprises
www.techtoystoday.com
-------------------------------------------------

What is the source of the material you are trying to program the  
EEPROM with? I think that needs to be a .elf file?

Timing (ISP  clock) should be no different than flash.

Jim Wagner
Oregon Research Electronics

On Jun 28, 2009, at 8:58 PM, dlc wrote:

>
>
> The EEPROM works fine - I can write and read it in a program, avrdude
> just won't write it during programming. Maybe a timing setting in
> avrdude can correct that?
>
> DLC
>
> Bob Paddock wrote:
> >> Has anyone seen this before and solved it? Is there a later  
> version of
> >> avrdude that fixes the problem? Am I simply doing something wrong?
> >
> > Have you tried a different part? We program a lot of Tiny2313 that
> > use section of the EEPROM, have not had any problems with AVRDude
> > doing it.
> >
> >
> >
>
> -- 
> Question with boldness even the existence of a God;
> because, if there be one, he must more approve of the
> homage of reason, than that of blind-folded fear.
> Thomas Jefferson
> -------------------------------------------------
> Dennis Clark TTT Enterprises
> www.techtoystoday.com
> -------------------------------------------------
>
>
> 



[Non-text portions of this message have been removed]

> What is the source of the material you are trying to program the
> EEPROM with? I think that needs to be a .elf file?

Newer version of AVRDude will work with .elf files, however
.hex files are usually used.


-- 
http://www.wearablesmartsensors.com/
http://www.softwaresafety.net/
http://www.designer-iii.com/
http://www.unusualresearch.com/

> What is the source of the material you are trying to program the
> EEPROM with? I think that needs to be a .elf file?
>
> Timing (ISP  clock) should be no different than flash.

When programming the EEPROM via ICSP the .eep file is the source of the
data - and I've found that the first two or three bytes properly program,
but then errors start.  I've confirmed that the file is correct, and that
the error given in avrdude's compare is also correct (in that the byte was
not programmed.)

DLC

> Jim Wagner
> Oregon Research Electronics
>
> On Jun 28, 2009, at 8:58 PM, dlc wrote:
>
>>
>>
>> The EEPROM works fine - I can write and read it in a program, avrdude
>> just won't write it during programming. Maybe a timing setting in
>> avrdude can correct that?
>>
>> DLC
>>
>> Bob Paddock wrote:
>> >> Has anyone seen this before and solved it? Is there a later
>> version of
>> >> avrdude that fixes the problem? Am I simply doing something wrong?
>> >
>> > Have you tried a different part? We program a lot of Tiny2313 that
>> > use section of the EEPROM, have not had any problems with AVRDude
>> > doing it.
>> >
>> >
>> >
>>
>> --
>> Question with boldness even the existence of a God;
>> because, if there be one, he must more approve of the
>> homage of reason, than that of blind-folded fear.
>> Thomas Jefferson
>> -------------------------------------------------
>> Dennis Clark TTT Enterprises
>> www.techtoystoday.com
>> -------------------------------------------------
>>
>>
>>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


-- 
Dennis Clark
TTT Enterprises

I had, on occasion, to change timings in the avrdude config file.
I just increased some... basically trying my luck, and sometimes I got 
lucky.

Cat

> I had, on occasion, to change timings in the avrdude config file.
> I just increased some... basically trying my luck, and sometimes I got
> lucky.

  This is what I'm wondering about - EEPROM writes take some special
cycles for proper timing when doing it pro grammatically via the avr
libc functions, I don't know what avrdude may do/need for it.

DLC

> Cat

-- 
Dennis Clark
TTT Enterprises