• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 376 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Hardware Trace Analyzer stack usage XDS560 Pro Trace

Judy Shen
Prodigy 130 points

I am using the hardware trace analyzers in CCS 6.1.1 with TMS570LC43xx target with the XDS560v2 Pro Trace receiver and debug probe on Windows 7 64-bit.

I have already found the Function Profiler and Code Coverage functionalities very useful.

Now I am trying to analyze the stack usage for the program running on the target device. I am aware of the static stack analysis options (ie call graphs). I also read through the Trace Analyzer guide which hints that crashes from stack overflows can be detected. I am interested in not just detecting overflows but actually analyzing usage of the stack during the program.  Is there any way to use the Pro Trace receiver and debug probe to run dynamic stack analysis? 

  • 0
    Prodigy 130 points
    An additional note: I have investigated
    1) using the stack pointer to estimate the stack usage and
    2) filling the stack memory with a pattern and using the memory browser to check how much of the initial pattern remains

    I am looking to see if there is a way to do is using the XDS560v2 Protrace!

    Thanks!