Re: [avr-gcc-list] Macro to read /write long to eeprom

[Peter Bosscha]

Ok, let's try to be more clear about this ..

 

Structure size is say 1000 Bytes, when writing the entire structure the write time would therefore be 9mSec * 1000 = 9 Seconds.

Typically in our situation, parts of the structure change but other parts stay the same (this is configuration data for a PLC-like device).

When downloading the entire structure from a PC, quite a bit of eeprom memory already contains the correct values.

So instead of waiting 9 Seconds for a full structure update (and another 9 seconds for a backup structure), we first read before write each byte, typically saving us quite a lot of time.

 

Clearer ?

 

Peter Bosscha

 

 

>>> address@hidden 10/08/2005 09:28:39 >>>

"Peter Bosscha" <address@hidden> wrote:

> We have large structures in eeprom, parts of which are saved/updated
> regularly. Doing a read before write saved us seconds in wait
> time.

Curious, can you explain that effect?  Is there any reference in the
datasheet about that?
--
J"org Wunsch                                           Unix support engineer
address@hidden        http://www.interface-systems.de/~j/


_______________________________________________
AVR-GCC-list mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list

--
This message is subject to the CSIR's copyright, terms and conditions and e-mail legal notice.
Views expressed herein do not necessarily represent the views of the CSIR.

CSIR E-mail Legal Notice

CSIR Copyright, Terms and Conditions

For electronic copies of the CSIR Copyright, Terms and Conditions and the CSIR Legal Notice
send a blank message with "REQUEST LEGAL" in the subject line to CSIR HelpDesk

This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.