Non-Confidential | ![]() | 100964_1142_00_en | ||
| ||||
Home > Plug-ins for Fast Models > Loading a plug-in into a model |
The method of loading a plug-in depends on the type of model being used.
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 <
switch. If more than one
plug-in is required, use multiple path_to_plugin
>/<plugin_name
>.so--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
to the plug-in path or
paths.<instancename>
=
Prebuilt plug-ins can be found at $PVLIB_HOME/plugins/<OS_compiler>
/.
Run the following command to list the model parameters, followed by the plug-in parameters:
FVP_Base_AEMv8A.exe --plugin="%PVLIB_HOME%\plugins\Win64_VC2013\Release\TarmacTrace.dll" --list-params
Run the following command:
FVP_Base_AEMv8A.exe -C bp.secure_memory=0 \ --plugin="%PVLIB_HOME%\plugins\Win64_VC2013\Release\TarmacTrace.dll" \ -C TRACE.TarmacTrace.trace-file=trace.log \ -a=startup_AEMv8-FVP_AArch64_AC6.axf
This command does the following:
TarmacTrace
plug-in
into the model using the model option --plugin
.TarmacTrace
log
file using the plug-in parameter TRACE.TarmacTrace.trace-file
.-a
.