| ??? 11/10/06 12:58 Read: times |
#127708 - If the internal POR/BOD isn't working correctly .. Responding to: ???'s previous message |
Brown outs may be the couse of my problems in some cases, even if I doubt that it causes the vast number of failures (still growing) the costomer reports.
If the internal circuitry doesn't protect the EEPROM, then it doesn't require an "actual" brown-out to cause trouble - simply powering the device on or off is enough for potentially corrupting the EEPROM. Are you using an RC reset circuit ? If yes, then you're looking at a good candidate for the source of your problems right there. RC resets are for toys only. Right now I'm not shure there is a real problem with either the hardware or the software at all. Maybe you could post an excerpt of your EEPROM write routines ? How often are you writing to the EEPROM ? Are you following the instructions/recommendations in the datasheet for handling the EEMWE bit ? |
| 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 |