Execution Trace and Execution Profile - which targets are supported?

Comments

2 comments

  • Avatar
    Michael Johnson

    Did you set the "Trace Interface Type" project property to "ETB"? Did you leave it running long enough - the ETM periodically sends out sync packets that the decode software must find in to do the decode.

    0
    Comment actions Permalink
  • Avatar
    Peter Lawrence

    Thanks!  Knowing that the "Trace Interface Type" parameter of the Project associated with the core with an ETB needs to be set to "ETB" is key.  (There are other options with said parameter that are undoubtedly applicable to other trace options.)

    For example, the Cortex-M4 on the LPC4370 does have an ETB, whereas the Cortex-M0 do not.  (Since there are example projects for the LPC-Link 2, is it worth setting that parameter to the right value to help the user?)

    As a trace "newbie", what I notice is that when the "Execution Trace" window has a "Source" pull-down control, there is the potential for trace data.  (The default setting for "Source" is "ITM", which doesn't seem to display anything.  However, "ETM" and "All" display data.)  If the "Source" control isn't present, the "Execution Trace" is just a tease.  The user can right-click to "Enable" and see "Running..." during execution, but these don't actually mean Execution Trace is supported for that particular target.

    Thanks!

    0
    Comment actions Permalink

Please sign in to leave a comment.