I am having problems with my accelerometer. It does some strange things after operating a long time (sometimes more than 30 days!) At this point, I have no idea even what state it is in then as some aspects continue in more or less normal operation. What I want to do is put it on the debugger and "break all" once it gets into this mode, to determine what states the port pins are in, and what pertinent variables indicate. There has never been any indication of stack overflow or buffer over-runs but I DO need to check those, once an event occurs..
The problem I need to figure out is how to keep the debugger running continuously for that time.
First issue is the dreaded Micro$oft update. I think that turning off WiFi should prevent that. Other ideas or Comments?
Second is sleeping. Using Win10, most recent update. Not a Windows person so not sure how to prevent sleep?
The host is a laptop so it should effectively be in a UPS. Will connect the Dragon directly to the laptop to avoid power drops on the externally powered USB hub. We get lots of power drops, here.
Anything else that I need to watch out for and possibly change, temporarily?
And a debugger question: Is there some way to do a (RAM) memory dump early in the operation then compare that with a memory dump after the fault occurs?
Oregon Research Electronics