| |||
| Home > Programmer’s Reference > Model configuration parameters > Profiling parameters | |||
If you have a license to use ARM Profiler, and your core tile RTSM supports profiling, you can collect and interpret profiling information when you run code. You can also specify the name of the resulting analysis file. The profiling information can be collected directly by ARM Profiler. See Getting started with ARM Profiler. Alternatively you can run the RTSM using a tool such as Model Debugger then load the resulting analysis file into ARM Profiler afterwards.
You cannot use RealView Profiler v1.x with RTSMs provided with RealView Development Suite v4.0, or System Canvas v4.0 or v4.0 SP1.
RealView Debugger does not support RTSM profiling, so you cannot generate an ARM Profiler analysis file even if you enable the profiling parameters.
All RTSMs can be built in System Canvas v4.0 SP1 to work with ARM Profiler v2.0. The EB RTSMs supplied with RealView Development Suite v4.0 also support ARM Profiler v2.0. Table 3.10 lists the profiler instantiation-time parameters that you can change when you start the model. The syntax to use in a configuration file is:
coretile.core.parameter=value
Table 3.10. Profiler instantiation parameters
| Parameter | Description | Type | Values | Default |
|---|---|---|---|---|
| profiler-enable | enables profiling at model instantiation | boolean | true/false | false[1] |
| profiler-output_file | sets the name of the ARM Profiler analysis file generated by the profiler, relative to the location of the RTSM | string | - | [empty string][2] |
[1] Profiling is assumed to be enabled if you are running the RTSM through ARM Profiler. [2] The default analysis
file name in ARM Profiler is
| ||||