• For an FVP, ISIM, SystemC EVS using scx::scx_parse_and_configure, or when using Model Shell or Model Debugger, specify the plug-in using the --plugin <path_to_plugin>/<plugin_name>.so switch. If more than one plug-in is required, use multiple --plugin switches.

  Specify plug-in parameters using the -C option when launching the FVP, or in a configuration file.

• Fast Models that are exported to SystemC have an API function scx::scx_load_plugin. This function allows you to hard-code the path to the plug-in in your SystemC code, before calling sc_start, as follows:

  scx::scx_load_plugin("$PVLIB_HOME/plugins/<OS_Compiler>/<plug-in_name>.so");

• When it is not possible to specify a trace plug-in to the launching tool, set the environment variable FM_TRACE_PLUGINS. This variable must point to the full path of the plug-in. For example:

  Linux

  export FM_TRACE_PLUGINS <installation_path>/plugins/<OS_Compiler>/TarmacTrace.so

  Windows

  set FM_TRACE_PLUGINS <installation_path>\plugins\<OS_Compiler>\TarmacTrace.dll

  To use multiple plug-ins at the same time, separate them with a semicolon. You can also load the same plug-in multiple times.

  Give the plug-in instance a name by adding the prefix <instancename>= to the plug-in path or paths.

Prebuilt plug-ins can be found at $PVLIB_HOME/plugins/<OS_compiler>/.