FDS garbage collection preventing app timer from feeding watchdog

RE: FDS garbage collection preventing app timer from feeding watchdog

Jared — Sat, 18 Apr 2020 08:36:20 GMT

I think that this confirms your assumption in that it's the garbage collection that prevents the app timer to reset the WD timer. You could try to queue the garbage collection right after the timer is reset in the app timer handler. This along with a no too strict timer requirement should give FDS enough time to complete the garbage collection before you have to feed the watchdog timer again. This will of course queue a lot of gc operations if you schedule them every time you reset the WD timer. Instead, you should figure out how often your application is in need of garbage collection based on your FDS operations. For example scheduling a garbage collection every 100th time you call the WD timer... Not sure if this is the best solution but might be a good start :)

RE: FDS garbage collection preventing app timer from feeding watchdog

jzplusplus — Thu, 16 Apr 2020 17:42:22 GMT

Increasing the watchdog timer seems to lessen how often the problem occurs but does not solve it entirely. I modified the code above to loop after garbage collection succeeds. With the watchdog timer set at 500 milliseconds, it successfully loops anywhere between 100 and 200 times, but still trips the watchdog at some point.

RE: FDS garbage collection preventing app timer from feeding watchdog

Jared — Thu, 16 Apr 2020 13:15:02 GMT

Hi,

Could you try to increase the Watchdog timer a bit and see if it helps? It might be to strict as the typical time it takes to erase one page is 85 ms.