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# 14019

ModelSim (SE, PE) SmartModel/SWIFT Interface - How do I use the MGT and PPC SmartModels in ModelSim?

Description


The Xilinx Virtex-II Pro 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.



How are these models used in ModelSim?



NOTE: For ISE 7.1i and above, please refer to the latest version of the Synthesis and Simulation Design Guide at:

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


NOTE: If using ModelSim SE/PE Version 6.1/a/b, see (Xilinx Answer 22214).

Solution


MTI ModelSim SE and ModelSim PE (5.7 or later) - Solaris 2.6/2.7/2.8



Simulator Setup

NOTE: When using ModelSim PE (5.7 or later), the SWIFT interface must be enabled. Please contact the vendor to enable this option.



Although ModelSim SE and ModelSim PE (5.7 or later) support the SWIFT Interface, certain modifications must be made to the default ModelSim setup to enable this feature.



You must make the following changes to the "modelsim.ini" file located in the "$MODEL_TECH" directory.



1. After the lines:

; Simulator resolution

; Set to fs, ps, ns, us, ms, or sec with optional prefix of 1, 10, or 100.



edit the statement that follows from "Resolution = ns" to "Resolution = ps."



2. After the lines:

; Specify whether paths in simulator commands should be described

; in VHDL or Verilog format. For VHDL, PathSeparator = /

; for Verilog, PathSeparator = .



comment the following statement by adding a semicolon (;) at the beginning of the line:

PathSeparator = /



3. After the line:

; List of dynamically loaded objects for Verilog PLI applications



add the following statement:

Veriuser = $MODEL_TECH/libswiftpli.sl



4. After the line:

; Logic Modeling's SmartModel SWIFT software (Sun4 Solaris 2.x)



add the following statements:

libsm = $MODEL_TECH/libsm.sl

libswift = $LMC_HOME/lib/sun4Solaris.lib/libswift.so



NOTE: It is important that you change the order in which the commands appear in the "modelsim.ini" file. The simulation might not work if you do not follow the order recommended above.



Running a Simulation

You can use the files in the "$XILINX/smartmodel/sol/simulation/mtiverilog or mtivhdl" directory to help you set up and run a simulation using the SWIFT Interface.



Once the simulator is set up, you must compile the SmartModel wrapper files into the UniSim and SimPrim libraries. You can do this by running CompXLib (command line library-compiling utility) with the -f virtex2p:m option. Enter "compxlib -help" on the command line for details on the specific command line needed for your system.



To verify that the SmartModels are set up correctly, enter the following in the ModelSim command window:



VSIM>vsim unisim.ppc405



If there are no errors upon loading, the simulator is set up correctly.



If you are using ISE 9.1i or later Please refer Solution 24800 (Xilinx Answer 24800).



MTI ModelSim SE and ModelSim PE (5.7 or later) - Windows 2000/XP



Simulator Setup

NOTE: When using ModelSim PE (5.7 or later), the SWIFT interface must be enabled. Please contact the vendor to enable this option.



Although ModelSim SE and ModelSim PE (5.7 or later) support the SWIFT Interface, you must make certain modifications to the default ModelSim setup to enable this feature.



You must make the following changes to the "modelsim.ini" file located in the "%MODEL_TECH%" directory:



1. After the lines:

; Simulator resolution

; Set to fs, ps, ns, us, ms, or sec with optional prefix of 1, 10, or 100.



edit the statement that follows, from "Resolution = ns" to "Resolution = ps."



2. After the lines:

; Specify whether paths in simulator commands should be described

; in VHDL or Verilog format. For VHDL, PathSeparator = /

; for Verilog, PathSeparator = .



comment the following statement by adding a semicolon (;) at the beginning of the line:

PathSeparator = /



3. After the line:

; List of dynamically loaded objects for Verilog PLI applications



add the following statement:

Veriuser=$MODEL_TECH/libswiftpli.dll



4. After the line:

; Logic Modeling's SmartModel SWIFT software (Windows NT)



add the following statements:

libsm = $MODEL_TECH/libsm.dll

libswift=$LMC_HOME/lib/pcnt.lib/libswift.dll



NOTE: It is important that you change the order in which the commands appear in the "modelsim.ini" file. The simulation might not work if you do not follow the order recommended above.



Running a Simulation

Use the files in the "%XILINX%\smartmodel\nt\simulation\mtiverilog or mtivhd" directory to help you set up and run a simulation using the SWIFT Interface.



Once the simulator is set up, you must compile the SmartModel wrapper files into the UniSim and SimPrim libraries by running CompXLib (command line library-compiling utility) with the -f virtex2p:m option. Enter "compxlib -help" on the command line for details on the specific command line needed for your system.



To verify that the SmartModels have been set up correctly, enter the following in the ModelSim command window:



VSIM>vsim unisim.ppc405



If there are no errors upon loading, the simulator is set up correctly.



NOTE: If you are running ModelSim Standalone with a ".mpf" file, make sure these changes are made in that file too.



MTI ModelSim SE and ModelSim PE (5.7 or later) - Linux



Simulator Setup

NOTE: When using ModelSim PE (5.7 or later), the SWIFT interface must be enabled. Please contact the vendor to enable this option.



Although ModelSim SE and ModelSim PE (5.7 or later) support the SWIFT Interface, certain modifications must be made to the default ModelSim setup to enable this feature.



You must make the following changes to the "modelsim.ini" file located in the "$MODEL_TECH" directory.



1. After the lines:

; Simulator resolution

; Set to fs, ps, ns, us, ms, or sec with optional prefix of 1, 10, or 100.



edit the statement that follows from "Resolution = ns" to "Resolution = ps."



2. After the lines:

; Specify whether paths in simulator commands should be described

; in VHDL or Verilog format. For VHDL, PathSeparator = /

; for Verilog, PathSeparator = .



comment the following statement by adding a ";" at the beginning of the line:

PathSeparator = /



3. After the line:

; List of dynamically loaded objects for Verilog PLI applications



add the following statement:

Veriuser = $MODEL_TECH/libswiftpli.sl



4. After the line:

; Logic Modeling's SmartModel SWIFT software (Linux)



add the following statements:

libsm = $MODEL_TECH/libsm.sl

libswift = $LMC_HOME/lib/x86_linux.lib/libswift.so



NOTE: It is important that you change the order in which the commands appear in the "modelsim.ini" file. The simulation might not work if you do not follow the order recommended above.



Running a Simulation

You can use the files in the "$XILINX/smartmodel/lin/simulation/mtiverilog or mtivhdl" directory to help you set up and run a simulation using the SWIFT Interface.



Once the simulator is set up, you must compile the SmartModel wrapper files into the UniSim and SimPrim libraries. You can do this by running CompXLib (command line library-compiling utility) with the -f virtex2p:m option. Enter "compxlib -help" on the command line for details on the specific command line needed for your system.



To verify that the SmartModels have been set up correctly, enter the following in the ModelSim command window:



VSIM>vsim unisim.ppc405



If there are no errors upon loading, then the simulator is set up correctly.
AR# 14019
Date Created 08/29/2007
Last Updated 05/10/2011
Status Archive
Type General Article