UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 25518

NC-VHDL, SmartModel/SWIFT Interface - How do I use the MGT and PPC SmartModels in NC-VHDL for ISE 9.1x and above?

Description

The Xilinx Virtex-II Pro Virtex-4 and Virtex- 5 simulation flow uses Synopsys VMC models to simulate the IBM PowerPC microprocessor and RocketIO multi-gigabit transceiver. Because VMC models are simulator-independent models derived from the actual design, they are accurate evaluation models. To simulate these models, you must use a simulator that supports the SWIFT interface.

In 5.2i/5.1i, you must install the SmartModels. For information related to SmartModel installation, see (Xilinx Answer 15501).

In 6.1i, the SmartModels are installed automatically.

In ISE 7.1i and above, CompXLib must be run first. For more information on CompXLib, refer to the Synthesis and Simulation Design Guide at:

http://www.xilinx.com/support/software_manuals.htm

How are these models used in NC-VHDL?

Solution

Running the simulation with Cadence NC-VHDL - Linux

Several files in the "$XILINX/smartmodel/lin/simulation/ncvhdl" directory can help you set up and run a simulation utilizing the SWIFT interface. A description of each file follows:

setup file - A description of variables that must be set for correct simulation.

For example:

setenv XILINX <Xilinx path>

setenv CDS_INST_DIR <Cadence path>

setenv LM_LICENSE_FILE <license.dat>:$LM_LICENSE_FILE

setenv LMC_HOME $XILINX/smartmodel/lin/installed_lin

setenv LMC_CONFIG $LMC_HOME/data/linux.lmc

setenv LD_LIBRARY_PATH $CDS_INST_DIR/tools/lib:$LMC_HOME/sim/pli/src:$LMC_HOME/lib/linux.lib:$LD_LIBRARY_PATH

setenv LMC_TIMEUNIT -12

setenv PATH ${LMC_HOME}/bin ${CDS_INST_DIR}/tools/bin ${PATH}

setenv PATH ${XILINX}/bin/lin ${PATH}

You are responsible for changing the parameters included within "< >" to match your system configuration.

simulate file - An example NC-VHDL compilation simulation script that illustrates which files must be compiled and loaded for simulation. You can modify this file to simulate a design by including the design and testbench files appropriately.

For example:

ncvhdl v93 <testbench>.vhd <design>.vhd

ncelab -work worklib -cdslib cds.lib -access +wc worklib.<testbench>:<view>

Note: If using IUS5.5 and higher, this command will change to:

ncelab -lib_binding -work worklib -cdslib cds.lib -access +wc worklib.<testbench>:<view>

ncsim +access+rw -gui -cdslib cds.lib worklib.<testbench>:<view>

You are responsible for changing the parameters included within "< >" to match your design files and testbench.

After you have updated each of these files, you can run the simulation.

Running the simulation with Cadence NC-VHDL - Solaris 2.6/2.7/2.8

Several files in the "$XILINX/smartmodel/sol/simulation/ncvhdl" directory can help you set up and run a simulation utilizing the SWIFT interface. A description of each file follows:

setup file - A description of variables that must be set for correct simulation.

For example:

setenv XILINX <Xilinx path>

setenv CDS_INST_DIR <Cadence path>

setenv LM_LICENSE_FILE <license.dat>:$LM_LICENSE_FILE

setenv LMC_HOME $XILINX/smartmodel/sol/installed_sol

setenv LMC_CONFIG $LMC_HOME/data/solaris.lmc

setenv LD_LIBRARY_PATH $CDS_INST_DIR/tools/lib:$LMC_HOME/sim/pli/src:$LMC_HOME/lib/sun4Solaris.lib:$LD_LIBRARY_PATH

setenv LMC_TIMEUNIT -12

setenv PATH ${LMC_HOME}/bin ${CDS_INST_DIR}/tools/bin ${PATH}

setenv PATH ${XILINX}/bin/sol ${PATH}

You are responsible for changing the parameters included within "< >" to match your system configuration.

simulate file - An example NC-VHDL compilation simulation script that illustrates which files must be compiled and loaded for simulation. You can modify this file to simulate a design by including the design and testbench files appropriately.

For example:

ncvhdl -v93 <testbench>.vhd <design>.vhd

ncelab -work worklib -cdslib cds.lib -access +wc worklib.<testbench>:<view>

Note: If using IUS5.5 and higher, this command will change to:

ncelab -lib_binding -work worklib -cdslib cds.lib -access +wc worklib.<testbench>:<view>

ncsim +access+rw -gui -cdslib cds.lib worklib.<testbench>:<view>

You are responsible for changing the parameters included within "< >" to match your design files and testbench.

After you have updated each of these files, you can run the simulation.

Running the simulation with Cadence NC-VHDL - Windows 2000/XP

Several files in the "%XILINX%\smartmodel\nt\simulation\ncvhdl" directory can help you set up and run a simulation utilizing the SWIFT interface. A description of each file follows:

setup file - A description of variables that must be set for correct simulation.

For example:

set XILINX = <Xilinx path>

set CDS_INST_DIR = <Cadence path>

set LM_LICENSE_FILE = <license.dat>;%LM_LICENSE_FILE%

set LMC_HOME = %XILINX%\smartmodel\nt\installed_nt

set LMC_CONFIG = %LMC_HOME%\data\pcnt.lmc

set PATH = %LMC_HOME%\bin;%CDS_INST_DIR%\tools\lib;%LMC_HOME%\sim\pli\src;%LMC_HOME%\lib\pcnt.lib;%PATH%

set LMC_TIMEUNIT = -12

You are responsible for changing the parameters included within "< >" to match your system configuration.

simulate file - An example NC-VHDL compilation simulation script that illustrates which files must be compiled and loaded for simulation. You can modify this file to simulate a design by including the design and testbench files appropriately.

For example:

ncvhdl -v93 <testbench>.vhd <design>.vhd

ncelab -work worklib -cdslib cds.lib -access +wc worklib.<testbench>:<view>

Note: If using IUS5.5 and higher, this command will change to:

ncelab -lib_binding -work worklib -cdslib cds.lib -access +wc worklib.<testbench>:<view>

ncsim +access+rw -gui -cdslib cds.lib worklib.<testbench>:<view>

You are responsible for changing the parameters included within "< >" to match your design files and testbench.

After you have updated each of these files, you can run the simulation.

These environment variables and setting can be set globally as well. If you set these globally, you must do so in the "System Environment Variables," not in the "User Environment Variables."

AR# 25518
Date Created 09/04/2007
Last Updated 12/15/2012
Status Active
Type General Article