after 12 Hours, 5223X demo baord hangs, no response from CPU

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

after 12 Hours, 5223X demo baord hangs, no response from CPU

474 Views
TVNAIDU
Contributor III


I am using MCF5223X (Coldfire) based demo baord with tiny web application (keep refresh for some readings from GPIO), after 12 Hours of running, board locksup, any idea how to find why board hangs?. no response from console also, CPU clogs, appreciated for any inputs.

Labels (1)
0 Kudos
3 Replies

339 Views
FridgeFreezer
Senior Contributor I

Is there any sort of watchdog timer or any other timer running? Is there anything storing variables/data in RAM that might run out of space?

 

You don't really give enough information about the system/software, what you've done already to try and find the fault, etc. Have you got a debugger you can pause the system and look at what's going on (maybe after ~11 hours?), make it print out status messages on the console at regular intervals, etc.?

0 Kudos

339 Views
J2MEJediMaster
Specialist I

Are you using an interrupt handler? If so, is it cleaning up the stack properly when it exits? If it does not, this creates a "leak" where the stack slowly expands in memory until it stomps on something critical. Easiest way to confirm this is to increase the stack size (if possible) and if the board runs longer, that's your culprit.

 

Or, as was suggested earlier, halt the board at 11 hours and snoop around with the debugger to check out where the top of the stack is, among other things.

 

---Tom

0 Kudos

339 Views
FridgeFreezer
Senior Contributor I

You could also try halving the clock frequency (if possible) and see if it takes twice as long to lock up.

0 Kudos