SET
Joined: 15 Nov 2005 Posts: 161 Location: Glasgow, UK
|
|
Posted: Fri Dec 07, 2007 10:27 am |
|
|
Quote: | Next I put in some test code that would print some status registers every time the main loop executed a PWM duty cycle update to see the status of the system at that time. Within a few minutes of adding that piece of test code I had one instance of the EEPROM write function called. Is there any way the two could be related? |
So you are saying that the PWM cycle update calls the EEPROM write function - this is probably what you would expect (so that system saves new PWM value). So do you mean that this call then caused EEPROM corruption? Can you get the system to echo back the values it is going to write to EEPROM? And then do an EEPROM read and echo that, to confirm it did write Ok?
So you would get something like:
PWM update command -> PWM changes -> EEPROM is updated, echo'ed back -> EEPROM is read back |
|