Xtreme run modes?

Xtreme supports running the design in three modes:

run mode:
  Run mode is generally used for acceleration testcases, where DUT runs in RCC engine
and Testbench runs in xsim simulator.The simulation performances in this case is generally determined by software components running in xsim simulator.

autorun mode:
  autorun mode is mostly used for in-circuit emulation and targetless emulation  modes.In autorun all the modules must be compiled for RCC engine and also all the clocks must be generated from axis_clkgen module.autorun ignores all CLI commands after HW swap, and any control must be done manually by pressing CTRL-C  and typing commands on CLI or through axis tbcall mechanism.

tbrun:
  tbrun is very similar to autorun(has all the requirements of driving clocks from axis_clkgen and no module can run in XSIM SW) except it enables behavioural
delay control.This mode is mainly used for TBA(Transaction based acceleration using xtremeTBA libraries) applications.
 i.e C1>##600 $stop; will be honoured.(ignored in autorun mode).

Please refer to Xtreme documentation for more details.
Thanks,
DGill

The run command ($rcc(run);) is used for acceleartion. It allows the DUT to execute in RCC engine, and the remaining parts of the design and testbench run in XSIM software simulator. In run mode, user can have delay control from the CLI.

The autorun command ($rcc(autorun);) allows the DUT to execute in In-Circuit Emulation (ICE)
mode. It enables internal clock generation. This gives you the highest performance possible in
Xtreme. We have two kinds of ICE, one is targetless emulation and the other one is target emulation.
In autorun, user can not have delay control from the CLI. The only way to stop $rcc(autorun); from the Command Line Interface (CLI) is to press the Ctrl-C key and swap back to simulation mode.

The $rcc(tbrun); command enables delay control in targetless emulation. $rcc(tbrun);
mode has both the performance of $rcc(autorun); mode and the flexible delay control of $rcc(run);
mode.

One should also consider PI (primary input) and PO(primary output) sychronization when using discussing these modes.

$rcc(run): Both PI and PO events are propagated and cause synchronization
$rcc(tbrun: Only PI events are propagated as scheduled, PO events are propagated only when there is a tbcall synchronization (axis_tbcall, tbcall region, DPI call).
$rcc(autorun): No PI or PO event synchronization can take place, only tbcall sync. is supported.

Also keep in mind that it is possible to dynamically switch design into different modes at run time, e.g. run to tbrun mode or vice-versa.

-ashutosh