Posted on May 05, 2018 at 20:50You're going to need to walk your code an identify memory usage and writes which could corrupt memory or go out of bounds.
You'd want to add checks and breakpoints in critical areas to sanity check pointers and indexes to ensure they don't go out of range, and secondary checks of the buffer getting corrupted to trap the failure as quickly as possible after it happens so you can zoom down and focus on specific portions of your code.
Make sure your stack is sufficiently large to manage your usual call tree, and any the would occur from interrupts. Quantify how much stack you are currently using.
Check memory as you enter and leave interrupts.
