Non-Confidential | ![]() | 100968_1180_00_en | ||
| ||||
Home > Using Model Debugger > Launching Model Debugger > Launching from the command line |
To launch Model Debugger from the command line, type modeldebugger
, with options and arguments.
Table 2-1 Command-line options
Short | Long option | Description |
---|---|---|
|
Set a limit on the number of system cycles for a simulation in non-GUI mode. Use the |
|
|
Start |
|
|
Start |
|
-T |
|
Set a time limit for a simulation in non-GUI mode. Use the |
|
|
Load the application file Note:For the application file to be displayed in the Model Debugger Select Targets dialog, you must also specify the remote CADI simulation. See the-c option. |
|
|
Set one model parameter. Specify it as a path naming the instance and the
parameter name using dot separators. For example, |
|
|
Connect to a remote CADI simulation. |
|
|
Use verbose messages if displaying message text for message classes |
|
|
Connect to remote CADI simulation using the following environment variables:
|
|
|
Print all application output to |
|
|
Use model parameters from the configuration file
|
|
|
Print the available options and exit. |
|
|
Specify the instance. |
|
|
Log all CADI calls into an XML logfile |
|
List possible connections to remote CADI simulations on the local machine and exit afterwards. Each simulation has a unique simulation ID. |
|
|
List target instances. |
|
-l |
|
List target instances and their parameters. |
|
|
Load the specified model. |
|
|
Run the simulation without displaying the GUI. |
|
|
Do not display the parameter configuration dialog at startup. |
|
|
Print all application output to |
|
|
Load the project file |
|
|
Suppress all Model Debugger output. |
|
Load specific trace plug-ins. The equivalent environment variable is |
|
|
|
Equivalent to |
|
|
Print the tool version and exit. |
|
|
Force registers with initial integer display to be hexadecimal format instead. |
|
|
Load the layout file |
|
|
Suppress the Select Target dialog box that normally appears when a model is loaded. Model
Debugger automatically connects to targets that have the |
Filenames and similar strings that are specified when starting Model Debugger from the command line must be within double quotes if there is white space in the string.
For example:
modeldebugger -a "cluster0.cpu0=my application.axf"
There is, however, no requirement to use quotes if the string has no spaces. Both of these forms are valid:
modeldebugger -a cluster0.cpu0=dhrystone.axf
modeldebugger -a "cluster0.cpu0=dhrystone.axf"
You can configure a model that you start from the command line with Model Debugger by including a reference to an optional plain text configuration file. Each line of the configuration file must contain the name of the component instance, the parameter to be modified, and its value.
Use this format:
instance.parameter=value
The
can be a hierarchical path, with each level
separated by a dot “.” character. If instance
is a
string, additional formatting rules might apply.value
You can include comment lines beginning with a #
character in your configuration file. Boolean values can be set
using either true
/false
or 1
/0
, for example:
# Disable semihosting using true/false syntax coretile.core.semihosting-enable=false # # Enable VFP at reset using 1/0 syntax coretile.core.vfp-enable_at_reset=1 # # Set the baud rate for UART 0 baseboard.uart_0.baud_rate=0x4800
Model Debugger can be run without a Graphical User Interface (GUI). This mode is triggered by the command-line option --nogui
.
To limit the duration of a simulation in non-GUI mode, specify the amount of seconds or system cycles using the command-line options:
--timelimit time_in_seconds
--cyclelimit number_of_system_cycles
The --timelimit
and --cyclelimit
options are only available in --nogui
mode.