Model Debugger for Fast Models User Guide : 2.1.1 Launching from the command line

2.1.1 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
	`--cyclelimit` `cycles`	Set a limit on the number of system cycles for a simulation in non-GUI mode. Use the `--nogui` option to enable this option.
	`--debug-isim` `isim_system`	Start `isim_system` and connect Model Debugger to the simulation.
	`--debug-sysc` `systemc`	Start `systemc` simulation and connect Model Debugger to the simulation.
`-T`	`--timelimit` `time`	Set a time limit for a simulation in non-GUI mode. Use the `--nogui` option to enable this option.
`-a`	`--application` `filename`	Load the application file `filename`. To target cores in cluster systems, prefix the name with the path to the instance. For example, `foo.bar.core=dhrystone.axf`. 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.
`-C`	`--parameter` `parameter`	Set one model parameter. Specify it as a path naming the instance and the parameter name using dot separators. For example, `foo.bar.inst.parameter=1000`. To set multiple parameters, use `--config-file`.
`-c`	`--connect` `simulation_id`	Connect to a remote CADI simulation. `simulation_id` specifies the simulation to connect to. `--list-connections` displays the list of available connections.
`-E`	`--enable-verbose msgClass`	Use verbose messages if displaying message text for message classes `msgClass`. Without an argument, this option lists all classes.
`-e`	`--env-connect`	Connect to remote CADI simulation using the following environment variables: `CADI_CLIENTPORT_TCP` – port number `CADI_INSTANCEID` – component instance name `CADI_APPLICATIONFILENAME` – application file name
`-F`	`--stdout-to-file` `FILE`	Print all application output to `FILE` instead of the StdIO pane in the Output Window.
`-f`	`--config-file` `filename`	Use model parameters from the configuration file `filename`.
`-h`	`--help`	Print the available options and exit.
`-i`	`--instance`	Specify the instance.
`-L`	`--cadi-log`	Log all CADI calls into an XML logfile `CADILog-nnnn.xml`, where `nnnn` is a set of four digits. The logfile is created in the same directory as the model.
	`--list-connections`	List possible connections to remote CADI simulations on the local machine and exit afterwards. Each simulation has a unique simulation ID.
	`--list-instances`	List target instances.
`-l`	`--list-params`	List target instances and their parameters.
`-m`	`--model` `filename`	Load the specified model.
`-N`	`--nogui`	Run the simulation without displaying the GUI.
`-n`	`--no-params-dialog`	Do not display the parameter configuration dialog at startup.
`-O`	`--stdout-to-stdout`	Print all application output to `stdout` instead of the StdIO pane in the Output Window.
`-p`	`--project` `filename`	Load the project file `filename`.
`-q`	`--quiet`	Suppress all Model Debugger output.
	`--plugin`	Load specific trace plug-ins. The equivalent environment variable is `FM_TRACE_PLUGINS`.
`-V`	`--verbose`	Equivalent to `--enable-verbose "MaxView"`.
`-v`	`--version`	Print the tool version and exit.
`-x`	`--force-reg-hex`	Force registers with initial integer display to be hexadecimal format instead.
`-Y`	`--layout` `filename`	Load the layout file `filename`.
`-y`	`--no-target-dialog`	Suppress the Select Target dialog box that normally appears when a model is loaded. Model Debugger automatically connects to targets that have the `executes_software` flag set. From the GUI, you can use the Other Settings check box in the Preferences dialog box to suppress the Select Target dialog box.

String syntax

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"

Configuration file syntax

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 instance can be a hierarchical path, with each level separated by a dot “.” character. If value is a string, additional formatting rules might apply.

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

Related references

String syntax

Running Model Debugger without a GUI

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.

Non-Confidential	PDF version	100968_1180_00_en
Copyright © 2014–2019 Arm Limited or its affiliates. All rights reserved.

2.1.1 Launching from the command line

Note:

String syntax

Configuration file syntax

Related references

Running Model Debugger without a GUI