Simulator Configuration Guide for Synopsys Models

Simulator Configuration GuideChapter 6: Using NC-VHDL with Synopsys ModelsAttentionFor best performance, use version 4.0 or later of NC-VHDL. NC-VHDLversion 4 and higher allow you to load multiple dynamic libraries containingC code. To use this means of loading the DWMM routines, include thefollowing option in the line invoking ncsim:ncsim -loadfmi libfmi_ml.so:slm_boot libfmi_ml.so (or .sl on HP-UX platforms) contains the library table andbootstrap function needed by the dynamic loader included in NC-VHDLversion 4.0 and above. This method eliminates the need to link libfmi_ar.awith your other external C (foreign language) modules to produce a singlelibfmi.so that incorporates all foreign language modules in a single library.For more information about using the NC-VHDL with multiple dynamiclibraries, see your Cadence simulator documentation.Using VERA and DesignWare Memory Models withNC-VHDLIf your NC-VHDL simulation includes DWMM models and VERA, you'll need tocreate a custom libfmi.so file.NoteNC-VHDL allows the bodies of VHDL entities and functions to be writtenin C and dynamically linked with the simulation executable at run time. AllC code must be in a single dynamic library named libfmi.so (solaris) orlibfmi.sl (HP-UX), and there must be a single fmiLibraryTable array in thelibfmi dynamic library file. The fmiLibraryTable contains the mapping ofVHDL element names to C code names, and must contain one entry for eachVHDL element to C code mapping.When combining C code for multiple products such as VERA, DWMMmodels, other vendor’s products, or your own C code, you must create a Csource file containing a fmiLibraryTable with mapping entries for eachproduct. The format of this array is discussed in your Cadence NC-VHDL Cuser document.If you use NC-VHDL version 4.0 or later, we recommend using its multiplefile loading mechanism.October 6, 2003 Synopsys, Inc. 117