| ??? 02/27/06 15:35 Read: times |
#110853 - that one code works does not prove that Responding to: ???'s previous message |
I have also observed that the corrupted eeprom had the same data in 2/3 occasions where I could check. However I rule out any software bug as the same software with the EEPROM write / read substituted with the I2C EEPROM access has been working without any problems.
that one code works does not prove that another is error free. Did you compare your code to the code generated by CodeArchitect? Now also, after this change we have had the unit running at our place for months before sending it to the field. Inspite of all this we see random failures in field. </i< stranslating the above statement: NOISE. Ever so many have things that run beautifully when not exposed to noise, but "misbehave" when noise is around. refer to the FAQ How can I resolve noise problems? Erik |
| Topic | Author | Date |
| P89LPC932A1 EEPROM corruption | 01/01/70 00:00 | |
| please explain | 01/01/70 00:00 | |
| LPC932 eeprom corruption | 01/01/70 00:00 | |
| depends on power supply | 01/01/70 00:00 | |
| lpc932A1 eeprom corruption | 01/01/70 00:00 | |
that one code works does not prove that | 01/01/70 00:00 |