Hi all,
I have a project up and running, its been going for along time now (2ish years) with constant dabbling from me! Just recently I had a few niggles when I rewrote the program with it hanging in funny places, this is now resolved but every so often when I check it its frozen (timescale has varied from a week to twice in 24 hrs). This hasn't happened before and I suspect it to be a I2C hang.
I have a display/keypad module, eeprom, rtcc on the I2C, I suspect it could be a bad connection to the keypad/display which I'm going to have a look at.
Its got me a bit spooked as the thing runs 24/7 feeding calves and I thought maybe I should be using the watchdog timer to force a reset if it happens again,
First question, will a watchdog reset force whichever I2C thing that could be hanging on to the bus to let go?
Are there any issues using the watchdog timer I should look out for?
I'm using a 18f2523 is there any way to tell if its a watchdog reset as opposed to a power off reset?
Cheers Geoff
I have a project up and running, its been going for along time now (2ish years) with constant dabbling from me! Just recently I had a few niggles when I rewrote the program with it hanging in funny places, this is now resolved but every so often when I check it its frozen (timescale has varied from a week to twice in 24 hrs). This hasn't happened before and I suspect it to be a I2C hang.
I have a display/keypad module, eeprom, rtcc on the I2C, I suspect it could be a bad connection to the keypad/display which I'm going to have a look at.
Its got me a bit spooked as the thing runs 24/7 feeding calves and I thought maybe I should be using the watchdog timer to force a reset if it happens again,
First question, will a watchdog reset force whichever I2C thing that could be hanging on to the bus to let go?
Are there any issues using the watchdog timer I should look out for?
I'm using a 18f2523 is there any way to tell if its a watchdog reset as opposed to a power off reset?
Cheers Geoff