Stack Watermark Release For Free

Save the current stack pointer value, and call the function of interest. Measure the stack high watermark, and compute the difference between the saved stack pointer value and the high watermark. This is the stack usage of the function.

Stack Usage. Stack Usage is performed by seeding the specified memory range with a pattern. Usage is considered to be a memory where pattern was overwritten. Stack Usage feature can only function in a bare-metal, non-OS application.

Using static code analyzers Developers can predict the stack use with a static code analyzer. Analysis tools can analyze function call depths, stack estimations on local variables and returns parameters, nested interrupts, and the size of interrupts occurring during execution.

Recursion. As with calling other functions, a recursive call may increase the size of the stack. A recursive call at the end of the function may increase the stack more than a recursive call near the beginning.

Stack Usage is performed by seeding the specified memory range with a pattern. Usage is considered to be a memory where pattern was overwritten. Stack Usage feature can only function in a bare-metal, non-OS application.

You can use ARM Compiler to determine how much stack space is used by the functions in your application code. The amount of stack that a function uses depends on factors such as the number and type of arguments to the function, local variables in the function, and the optimizations that the compiler performs.

You can increase StackUsageMax to raise the number of variables allocated to stack memory. If your target hardware has sufficient stack space, this reduces the amount of variables that are spilled off the stack. You can decrease StackUsageMax to reduce the number of variables allocated to stack memory.