What was the calling function of the code that caused the fault? Read more about how to quickly locate the cause of hard faults. What do you do after a system crash, especially when it happens very rarely and perhaps only after hours of execution? You need to discover what characteristics of the code triggered this exception? What code was being executed when the exception occurred? This is useful for bare-metal system, but even more so for RTOS-based designs where each task is assigned its own stack.
The result is that the worst-case scenario In terms of stack usage can be predicted. The static stack analyzer feature not only prints the stack usage for each function in the project but, more importantly, it can also analyze the elf-file and visualize the complete call graph for all entry points into the application.
You can quickly determine how much memory is used by your application and then drill down to see how the memory is used. Save time, find bugs faster, improve the performance of your system, and gain new insights. At the core of any successful embedded project are the tools you rely on every day to effectively and efficiently integrate hardware and software into a working system.
0 kommentar(er)
