Posted on July 15, 2016 at 02:21The common sense guidelines would be to understand how much memory you plan on malloc()ing, and how deep your call tree gets, and how large auto/local variables are.
Keil creates a static call graph in a .HTM file generated by the Linker.
Dynamically you can track malloc/free to get an idea of usage and maximal values. The stack depth can be checked, fill it with a marker character and review it periodically.
