RE: [avr-gcc-list] problem with EEPROM

[Iztok Zupet]

Hi,

And if You re overclocking the AVR, You must add aditional delay after
write (before another write or read).The eeprom ready flag is generated
with clok!.

Regerds
iz

On Sat, 2002-09-21 at 20:23, Geir Tore Olsen wrote:
> Hi There!
> 
> Corruption of the EEPROM is a well known problem with the AVR's. This is
> easily solved with using an external brownout circuit. I.E. a circuit that
> make sure that the controller is kept reset everytime the voltage is to low,
> and that make sure that the circuit is kept reset until the voltage is high
> enough.
> 
> Regards gtoo
> 
> -----Original Message-----
> From: address@hidden [mailto:address@hidden
> Behalf Of Juraj Buliscak
> Sent: Monday, September 16, 2002 8:41 AM
> To: address@hidden
> Subject: [avr-gcc-list] problem with EEPROM
> 
> 
> Hi all,
> 
> 
> I am using AT90S2313.  In EEPROM on address 0x01 is written value 0xAA in
> variable "val". Write process is OK. This is verified by downloadin eeprom
> section using uisp eeprom download.
> 
> Now I want to read value of variable val from eeprom.
> I use eeprom_rb function to read this value:
> 
> value = eeprom_rb((uint16_t)&val)
> 
> Problem is: after reading, value in eeprom is changed to 0xFF and eeprom_rb
> is returning 0xFF not 0xAA.  I do not  know where is problem. I downloaded
> eeprom by uisp after calling eeprom_rb and value on address 0x01 was
> changed to 0xFF.
> 
> Could anybody help?
> 
> Juraj.
> 
> 
> avr-gcc-list at http://avr1.org
> 
> 
> avr-gcc-list at http://avr1.org
> 
> 


avr-gcc-list at http://avr1.org