5.2.3 Building the EVS

This section describes how to build an Exported Virtual Subsystem (EVS).

System Canvas automatically uses the include path $SYSTEMC_HOME/include. The TPIP package installation process sets the SYSTEMC_HOME environment variable. To use a different copy of SystemC, modify the variable before starting System Canvas.

Procedure

  1. In System Canvas, enable the target option SystemC component under the menu entry ProjectProject SettingsTargets.
  2. Add the ports you require on the SystemC component as normal Fast Models ports.
  3. Add the headers and library files specified for your operating system.
  4. Build the SystemC component outside of System Canvas by invoking System Generator.
    simgen -p MySubsystem.sgproj --configuration AConfig -b
    SystemC executables made from the examples do not use the Post Build Actions for the linker in the Project Settings dialog. It is not possible to build and run these examples directly from System Canvas. Instead, the examples produce a SystemC executable by invoking System Generator from a Makefile. For Linux, your SystemC files are linked against the EVS generated files by the Makefile. For Microsoft Windows, the file is nMakefile.
    The built files are:
    Linux
    Shared library
    libMySubsystem-AConfig.so.
    Static library
    libscx-MySubsystem-AConfig.a.
    Header file
    AConfig/gen/scx_evs_MySubsystem.h.
    Static library
    libscx.a, containing the MI simulation infrastructure scheduler mapping, simulation controller and report handler default implementations.
    Microsoft Windows
    Shared library
    MySubsystem-AConfig.dll.
    Static library
    MySubsystem-AConfig.lib.
    Header file
    AConfig/gen/scx_evs_MySubsystem.h.
    Static library
    scx.lib, containing the MI simulation infrastructure scheduler mapping, simulation controller and report handler default implementations.
Non-ConfidentialPDF file icon PDF versionARM DUI0835I
Copyright © 2014-2016 ARM Limited or its affiliates. All rights reserved.