restore-snapshot run-command-file – deprecated
Simics Reference Manual  /  3 Commands  /  3.2 Command List  / 

run

Synopsis

run [count] ["unit"] [-non-blocking]

Description

Starts running the simulation. If the count argument is provided, Simics will execute count number of time units on the currently selected frontend processor and then stop. The time unit, provided by the unit argument, can be one of steps, cycles, s, ms, us, ns, ps, m or h. If no time unit is supplied, count is interpreted as steps if supported by the frontend processor, or else as cycles.

The command will raise an error if the simulation is already running.

When it is needed to reach a specified point in the simulation time one can use commands bp.time.run-until and bp.cycle.run-until that accept the -absolute flag. See the documentation of these command for information about their usage.

When used in a script, the run command will block further script execution until the simulation stops, similar to other CLI commands. This behavior can be overridden by the -non-blocking flag, that also has the side-effect of exiting all script execution. This flag is typically used at the end of a script to start simulation and still get an interactive command line.

Unlike other commands, the run and run-cycles commands will not block the command line when run interactively.

In script branches, the command will not block the script execution when run without the count argument. It will instead continue executing the next command as soon as the simulation has been started. When run with the count argument, the command will block until reaching the specified point in time.

Provided By

Simics Core

See Also

step-instruction, run-cycles, bp.time.run-until, bp.cycle.run-until
restore-snapshot run-command-file – deprecated