Execution Trace and Execution Profile - which targets are supported?
Should the Execution Trace functionality in 3.x work with a LPC4370 (LPC-Link 2 PCB) target?
It seems regardless of the target, the Execution Trace and Execution Profile windows give the user the illusion of that they are on the cusp of displaying something, but then they don't. The "Executing trace initialization" message during a download to a LPC4370 also gives the user the (false?) hope that the feature should work.
On a target that simply doesn't support these features, it seems desirable to show this unavailable state to the user. However, ostensibly the LPC4370 has an ETB, so shouldn't the user see something in these windows?
Thanks.
-
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!
Please sign in to leave a comment.
Comments
2 comments