Code Profiling
In this topic:
If you choose to profile code, Automatic Trace Configuration will set the trace logic to record the program execution/flow.
Make sure that Profiler is checked in Analyzer Configuration / Recorder page. |
Navigate to App/MCU / Profiler page and enable Code. You can:
•Select cores you want to be recorded/analyzed
It is recommended to select functions of interest and this way speed up the analysis. If you wish to profile all functions, leave the list empty, all functions will be profiled.
![]()
|
Select those cores that you want to be recorded/analyzed. For example, select which cores from the SMP configuration will be used for tracing.
![]()
|
This dialog enables adding a new area specify a function or a collection of functions, either in the download file or a specific module. These areas will be used to automatically filter the function profiler results and therefore speed up the analysis.
Select an are you wish to profile:
•All Functions
•All Functions in download file
•All Functions in Module
•Function or Routine
Multiple functions areas can be specified with a wild card.
•* - any sequence of characters
•? - any single character
•# - any single digit
•[set] - any of the characters in the set
•[!set] - none of the characters in the set
A set is defined as a sequence of characters. If a dash is used, all characters within the range qualify, e.g. [a-z] defines all characters in range a to z.
![]() |
This dialog Profiler Area enables editing entry and exit points.
![]() |