defenestrated
Member
Hi all,
I have a fairly large/complicated project (two teensy 3.6's running six stepper motors in synchrony) and it's all working great... mostly.
It works flawlessly for an unknown period of time –*at least a few days –*and then mysteriously stops. Which feels to me like a memory leak, especially since if I reset both teensys via TyCommander, it starts up again fine.
I know that the REAL answer is to pore through the code line by line and try to figure out where the dynamic memory allocations are not being freed, but since I'm limited in time and resources, I'm thinking that I may instead (or, first) try and implement an automatic reset, once a day, and see if that's enough.
I found this thread, which I imagine works, but will this have the same effect as a "hard" reset in terms of memory? Or should I need to build in an external hardware watchdog to be sure?
Related, anyone have any good recommendations for a hardware watchdog or timer?
Thanks all!
-Sam
I have a fairly large/complicated project (two teensy 3.6's running six stepper motors in synchrony) and it's all working great... mostly.
It works flawlessly for an unknown period of time –*at least a few days –*and then mysteriously stops. Which feels to me like a memory leak, especially since if I reset both teensys via TyCommander, it starts up again fine.
I know that the REAL answer is to pore through the code line by line and try to figure out where the dynamic memory allocations are not being freed, but since I'm limited in time and resources, I'm thinking that I may instead (or, first) try and implement an automatic reset, once a day, and see if that's enough.
I found this thread, which I imagine works, but will this have the same effect as a "hard" reset in terms of memory? Or should I need to build in an external hardware watchdog to be sure?
Related, anyone have any good recommendations for a hardware watchdog or timer?
Thanks all!
-Sam