|Home > Fast Models examples > SystemCExport examples|
Components and platform models that are created by exporting LISA+ components or platforms to SystemC. Also, bridge components for converting transactions between LISA+ protocols and SystemC.
Table 6-7 SystemCExport examples
LISA+ source for bridge components. For more information, see 3.1 Bridge components.
Source files and makefile rules that are common to the EVS and SVP examples.
Header files that are required for the export of LISA+ protocols to SystemC.
LISA+ files and project files for EVS (Exported Virtual Subsystem) components. These are LISA+ components with a SystemC wrapper and bridges that allow them to be used in an SVP.
Build the component to generate the header file and libraries required to include it in a SystemC simulation.
LISA+ source, build scripts, and makefiles for EVS platform examples.
An EVS platform is a LISA+ platform that has been exported as a SystemC object to allow it to be integrated into a SystemC simulation.
The EVS platform examples are minimal platforms that are designed for a specific use case, for example running the Dhrystone benchmark application or booting Linux.
The Dhrystone images dhrystone_v8.axf and dhrystone.axf for Armv7, are provided in the Fast Models Third Party IP package. They are loaded from $PVLIB_HOME/images/.
For more information about building EVS platforms, see Building Fast Models in the Fast Models User Guide.
SVPs (SystemC Virtual Platforms) are platform models in which each component or subsystem has been individually exported to SystemC using the Fast Models Multiple Instantiation (MI) feature. For more information, see Building an SVP in the Fast Models User Guide.
SVP platforms can be modified by replacing EVS components with other Fast Models EVSs, or with native SystemC components. There are three subdirectories: