??? 06/04/04 12:51 Read: times |
#71746 - RE: Serial EEPROM problem Responding to: ???'s previous message |
"Can anyone check this code for me ?"
I see no code, only a chain of functions. Without knowing, what happens inside these functions, there is no way to help. But I thing, most of these return something. So calling with ignoring every return informations was a very bad practice to see whats wrong. "// wait for acknowledge" if this comment describe exactly what happens, then your program would hang forever on only a single transmission fault. Typically any wait should be limited by a timeout. So any program can return with an error code, if something goes wrong temporary (e.g. because noise, spikes). Peter |
Topic | Author | Date |
Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
RE: Serial EEPROM problem | 01/01/70 00:00 | |
Problem Solved!!!!!![]() | 01/01/70 00:00 |