Hello,

I'm currently working on a project which includes a 24LC16B I2C
EEPROM and a serial RS485 connection. The communication on the serial
connection includes commands to directly write and read the contents
in the EEPROM. When developing the software, I did a testprogram
which constantly, by commands on the serial connection from a PC,
writes a random value to the EEPROM and verifies that it can be read
back. There is a counter which keeps track of how many times this has
been done. The PC also writes a log-file where I can see any errors
that has been detected (serial comm errors, eeprom verification
error). I have run this routine at nights and weekends to see when
the EEPROM failed. At first I thought there was something wrong with
the software because the EEPROM never failed. But at last, this
weekend, after about 12000000 (twelve million) write cycles to the
EEPROM i started to get verification errors. This took a couple of
weeks since the serial connection is only 2400 bps.

Just thought I let You know...


==============================
Ruben Jvnsson
AB Liros Elektronik
Box 9124, 200 39 Malmv, Sweden
TEL INT +46 40142078
FAX INT +46 40947388
ruben@pp.sbbs.se
==============================