2.10.3.2. Custom Simulation Scripts
You can automate simulations by creating customized scripts. You can generate scripts manually. In addition, you can use NativeLink to generate a simulation script as a template and then make the necessary changes. The following table shows a list of script directories NativeLink generates.
|   Simulator  |  
        Simulation File  |  
        Use  |  
     
|---|---|---|
|   Mentor Graphics* ModelSim* or QuestaSim*  |  
        /simulation/ modelsim/modelsim_setup.do Or mentor/msim_setup.tcl  |  
        Source directly with your simulator. Run do msim_setup.tcl, followed by ld_debug. If you have more than one IP, each IP has a dedicated msim_setup.tcl file. Make sure that you combine all the files included in the msim_setup.tcl files into one common msim_setup.tcl file.  |  
     
|   Aldec* Riviera Pro  |  
        /simulation/ aldec/rivierapro_setup.tcl  |  
        Source directly with your simulator . |  
     
|   Synopsys* VCS  |  
        /simulation/synopsys/vcs/vcs_setup.sh  |  
        Add your testbench file name to this file to pass the testbench file to VCS using the –file option. If you specify a testbench file for NativeLink and do not choose to simulate, NativeLink generates a script that runs VCS.  |  
     
|   Synopsys VCS MX  |  
        /simulation/synopsys/vcsmx/vcsmx_setup.sh  |  
        Run this script at the command line using quartus_sh–t <script> . Any testbench you specify with NativeLink is included in this script.  |