AVR-Chat

Hi all,

   I've looked at everything that I have found on the 'net and tried a 
fuse setting, sending 16 bit data to the EEPROM, whatever.  Here is the 
results of my last experiment.  Oh, avrdude version 5.5 is what I'm using.

Using the avr libc EEPROM routines I have this line of code:

unsigned char EEMEM ea[10] = {1,2,3,4,5,6,7,8,9,10};

Just like it says in the documentation.  When I look at the .eep file 
generated by avr-gcc it is correct and has it all there.  When I send it 
to the chip I get a verify error on byte 0x02.  Reading back the EEPROM 
to look at it I see this is what is in the EEPROM:

0x1,0x2,0x5,0x6,0x5,0x6,0x9,0xa,0x9,0xa,0xff...0xff

Hmm.  Why did avrdude do that?  This clearly looks wrong!  When I write 
this sequence in a program and read it back it is correct in EEPROM, 
avrdude is definitely the culprit unless I'm just doing something wrong.

Thanks all for any suggestions!
DLC
-- 
Q-------------------------------------------------
Dennis Clark          TTT Enterprises
www.techtoystoday.com
-------------------------------------------------