| ??? 11/08/06 14:52 Read: times |
#127563 - AT89S8253 EEPROM data loss |
Hi everybody
I have a hard-to-specify problem, reported from customer, in our first application to hit the market with the Atmel AT89S8253 chip. The customer have a substantial number of failing units. In previous releases of the product we used an external EEPROM on the SPI bus, where we now use the internal memory. The symptoms tell me that some E2 locations may be overwritten by faulty/random values after some time. The failing units are reported to behave well as soon as new configuration data are stored. I have examined my code very carefully, and done lots of tests, but I cannot reproduce the erroneous behaviour. I'm getting a bit desperate now, and I have started to look for explenations outside of my code. Have any of you experienced data loss from internal EEPROM? Could it possibly be caused by EMC, or would an EMC discharge have ruined the processor or E2 memory completely ? Are there any well known traps in handeling internal EEPROM? Could data be written in such way that it isn't durable? Any ideas are welcome! My best /Fredrik |
| Topic | Author | Date |
| AT89S8253 EEPROM data loss | 01/01/70 00:00 | |
| Standard question #1: | 01/01/70 00:00 | |
| nonstandard question #1 & #2 | 01/01/70 00:00 | |
| Brown outs | 01/01/70 00:00 | |
| now where have I seen that... | 01/01/70 00:00 | |
| so, that is sill the case | 01/01/70 00:00 | |
| Check the errata | 01/01/70 00:00 | |
| do you remember the first 932 ? | 01/01/70 00:00 | |
| Still not able to reproduce the error | 01/01/70 00:00 | |
| If the internal POR/BOD isn't working correctly .. | 01/01/70 00:00 | |
| if that is possible | 01/01/70 00:00 | |
| External reset chip and and and | 01/01/70 00:00 | |
| i agree half the way | 01/01/70 00:00 | |
I see what you mean.. | 01/01/70 00:00 |