> -----Original Message-----
> From: piclist-bounces@mit.edu On Behalf Of Robert James Kaes
> Sent: Friday, December 17, 2004 11:48 AM
>
> I thought I understood the refresh requirement, but I guess I was
> unclear about the cycle limit.  The way I read the datasheet was that if
<snip>
> So, in my application where the EEPROM value is updated once every two
> seconds, I would see a failure rate after approx. 23 days.
>
>   1M cycles / ((30 cycles/min) * 60min/hour * 24hour/day) =~ 23 days
>
> Is my understanding of how the EEPROM work correct now?  There is no way
> for an EEPROM to work "forever"?

Correct, if you must write to one storage location every two seconds, you
should use a different storage technology. Nothing will work forever but,
RAM and disk drives have a much greater write endurance than EPROM's.

If you have extra space in EEPROM you could also use multiple locations to
spread the wear and gain a longer life span.

Hope this helps,
Paul Hutchinson

>
> Thank you for your time.
> 	-- Robert

_______________________________________________
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist