MAX+PLUS II ACCESS Key Guidelines
List by VendorList by ToolList by FunctionViewlogic TopicsFusion/VCS Topics


Using Viewlogic Fusion/VCS & MAX+PLUS II Software

  Viewlogic logo

The following topics describe how to use the Viewlogic Fusion/VCS software with MAX+PLUS® II software. Click on one of the following topics for information:

This file is suitable for printing only. It does not contain hypertext links that allow you to jump from topic to topic.

Setting Up the MAX+PLUS II/Viewlogic Powerview Working Environment

  • Software Requirements
  • MAX+PLUS II/Viewlogic Powerview Interface File Organization
  • Viewlogic Powerview viewdraw.ini Configuration File
  • MAX+PLUS II/Viewlogic Powerview Project File Structure
  • Altera-Provided Logic & Symbol Libraries
  • The vdpath & mega_lpm Libraries

Simulation

  • Project Simulation Flow
  • Initializing Registers in VHDL & Verilog Output Files for Power-Up before Simulation
  • Performing a Timing Simulation with Fusion/VCS for Powerview Software
Go to: Go to the following MAX+PLUS II ACCESSSM Key topics for related information:
  • Compiling Projects with MAX+PLUS II Software
  • Programming Altera® Devices

  Go to the following topics, which are available on the web, for additional information:
  • MAX+PLUS II Development Software
  • Altera Programming Hardware
  • Viewlogic web site (http://www.Viewlogic.com)


Setting Up the MAX+PLUS II/Viewlogic Powerview Working Environment

To use the MAX+PLUS® II software with Viewlogic's Powerview software, you must install the MAX+PLUS II software, familiarize yourself with the Altera® Toolbox in the Powerview Cockpit, and then establish an environment that facilitates entering and processing designs. The MAX+PLUS II/Viewlogic Powerview interface is installed automatically when you install the MAX+PLUS II software on your workstation.

To set up your working environment for the MAX+PLUS II/Viewlogic Powerview interface, follow these steps:

  1. Ensure that you have correctly installed the MAX+PLUS II and Viewlogic software versions described in MAX+PLUS II/Viewlogic Powerview Software Requirements.

  2. Add the following environment variable to your .cshrc file to specify /usr/maxplus2 as the MAX+PLUS II system directory:

    setenv ALT_HOME /usr/maxplus2 ENTER

  3. Add the $ALT_HOME/Viewlogic/standard, $ALT_HOME/bin, and $ALT_HOME/Viewlogic/bin directories to the PATH environment variable in your .cshrc file.

  4. Add the $ALT_HOME/Viewlogic/standard directory to the WDIR environment variable in your .cshrc file using the following syntax:

    setenv WDIR $ALT_HOME/Viewlogic/standard:/<Powerview system directory>/standard ENTER

    NOTE: Make sure the $ALT_HOME/Viewlogic/standard directory is the first directory in your WDIR path.

  5. Source your .cshrc file by typing source .cshrc ENTER at the UNIX prompt.

  6. Create the Viewlogic Powerview viewdraw.ini configuration file.

  7. Copy the /usr/maxplus2/maxplus2.ini file to your $HOME directory:

    cp /usr/maxplus2/maxplus2.ini $HOME ENTER

    chmod u+w $HOME/maxplus2.ini ENTER

    NOTE: The maxplus2.ini file contains both Altera- and user-specified initialization parameters that control the MAX+PLUS II software, such as MAX+PLUS II symbol and logic function library paths and the current project name. The MAX+PLUS II installation procedure creates and copies the maxplus2.ini file to the /usr/maxplus2 directory.

    Normally, you do not have to edit your local copy of maxplus2.ini, because the MAX+PLUS II software updates the file automatically whenever you change any parameters or settings. However, if you move the max2lib and max2inc library subdirectories, you must update the file. Go to "Creating & Using a Local Copy of the maxplus2.ini File" in MAX+PLUS II Help for more information.

  8. If you plan to instantiate Library of Parameterized Modules (LPM) functions in ViewDraw schematics, you must create a new file with the name vdraw.vs. The vdraw.vs file must include the following line:

    load ("vdpath")

    You must also make sure that you specify the vdraw.vs file in your WDIR path.

  9. Set up a directory structure that facilitates working with the MAX+PLUS II/Viewlogic Powerview interface. Refer to MAX+PLUS II/Viewlogic Powerview Project File Structure.

NOTE: Go to MAX+PLUS II Installation in the MAX+PLUS II Getting Started manual for more information on installation and details on the directories that are created during MAX+PLUS II installation. Go to MAX+PLUS II/Viewlogic Powerview Interface File Organization for information about the MAX+PLUS II/Viewlogic Powerview directories that are created during MAX+PLUS II installation.

  Go to the following topics, which are available on the web, for additional information:
  • MAX+PLUS II Getting Started version 8.1 (5.4 MB)
  • This manual is also available in 4 parts:
    • Preface & Section 1: MAX+PLUS II Installation
    • Section 2: MAX+PLUS II - A Perspective
    • Section 3: MAX+PLUS II Tutorial
    • Appendices, Glossary & Index


MAX+PLUS II/Viewlogic Software Requirements

The following applications and utilities are used to generate, process, synthesize, and verify a project with MAX+PLUS® II and Viewlogic software.

Viewlogic Altera
VHDL Analyzer ViewTrace
MAX+PLUS II
version 10.0
Vantage VHDL Analyzer ViewData Path  
VHDL -> sym MOTIVE version 5.1.6  
edifneto SDF2MTV (optional)  
edifneti Fusion/VCS  
EEDIF (optional) vsm  
MMP (optional) ViewPath (optional)  

NOTE: The MAX+PLUS II read.me file provides up-to-date information on which versions of Viewlogic applications the current version of the MAX+PLUS II software supports. It also provides information on installation and operating requirements. You should read the read.me file on the CD-ROM before installing the MAX+PLUS II software. After installation, you can open the read.me file from the MAX+PLUS II Help menu.


MAX+PLUS II/Viewlogic Powerview Interface File Organization

Table 1 shows the MAX+PLUS® II/Viewlogic Powerview interface subdirectories that are created in the MAX+PLUS II system directory (by default, the /usr/maxplus2 directory) during MAX+PLUS II installation.

Note: For information on the other directories that are created during MAX+PLUS II installation, see "MAX+PLUS II File Organization" in MAX+PLUS II Installation in the MAX+PLUS II Getting Started manual.

Table 1. MAX+PLUS II Directory Organization

Directory Description
./lmf Contains the Altera-provided Library Mapping File, vwlogic.lmf, that maps Viewlogic logic functions to equivalent MAX+PLUS II logic functions.
./Viewlogic Contains the alt_edif.cfg EDIF configuration file that is used with the edifneti utility. Also contains the library and sample subdirectories.
./Viewlogic/examples Contains the sample Viewlogic designs.
./Viewlogic/library/max2sim Contains the MAX+PLUS II simulation model library (max2_sim) for use in ViewSim software.
./Viewlogic/library/alt_max2 Contains MAX+PLUS II primitives (EXP, GLOBAL, LCELL, SOFT, CARRY, CASCADE, DFFE, DFFE6K, and OPNDRN), macrofunctions (a_8fadd, a_8mcomp, a_8count, a_81mux), and megafunctions (clklock) for use in ViewDraw schematics. These logic functions support specific architectural features of Altera® devices. The alt_max2 library also contains modified versions of the ViewDraw primitives that use tri-state buffers, because these primitives require special handling in the MAX+PLUS II/Viewlogic Powerview interface.
./Viewlogic/library/synlib Contains the Altera-provided synthesis library altera, which includes MAX+PLUS II primitives, the altera.sml file, a sym directory, and a wir directory for use with ViewSynthesis software.
./Viewlogic/library/alt_mf Contains the VHDL models for the MAX+PLUS II primitives (EXP, GLOBAL, LCELL, SOFT, CARRY, CASCADE, DFFE, and OPNDRN), macrofunctions (clklock) for use with ViewSynthesis software, the Vantage VHDL Analyzer software, and the VHDL source files. These logic functions are used to maintain portability to other architectures.
./Viewlogic/library/alt_time Contains MOTIVE timing models for MAX+PLUS II logic functions (motive.lib), including the clklock megafunction, and MAX+PLUS II driver models (motive.drv).
./Viewlogic/library/alt_vtl Contains the VHDL source files for the VITAL 3.0-compliant library. This library is available for ViewSim software.
./Viewlogic/bin Contains all MAX+PLUS II, Viewlogic, and interface-related scripts.
./Viewlogic/standard Contains all standard .ini files and standard tools.

Go to: Go to the following topics, which are available on the web, for additional information:
  • MAX+PLUS II Getting Started version 8.1 (5.4 MB)
  • This manual is also available in 4 parts:
    • Preface & Section 1: MAX+PLUS II Installation
    • Section 2: MAX+PLUS II - A Perspective
    • Section 3: MAX+PLUS II Tutorial
    • Appendices, Glossary & Index


Viewlogic Powerview viewdraw.ini Configuration File

Each Powerview project is configured with the viewdraw.ini file that resides in the project directory. The DIR statements at the end of viewdraw.ini are paths to library directories that are used by the various Powerview applications. Figure 1 shows a sample of the DIR statements that are required to use the libraries.

Figure 1. Excerpt from viewdraw.ini

DIR [pw] .
DIR [r] /usr/maxplus2/vwlogic/library/alt_max2 (alt_max2)
DIR [r] /usr/maxplus2/vwlogic/library/max2sim (max2_sim)
DIR [r] /usr/maxplus2/vwlogic/library/synlib (altera)
DIR [r] /usr/maxplus2/vwlogic/library/alt_mf (alt_mf)
DIR [r] /usr/maxplus2/vwlogic/library/alt_vtl (alt_vtl)
DIR [rm] /<Powerview system directory>/lib/builtin (builtin)
DIR [rm] /<Powerview system directory>/simmods/vl/dip/74ls (vl74ls)
DIR [rm] /<Powerview system directory>/symsets/vl/dip/74ls (vl74ls)
DIR [r] /<Powerview system directory>/lib/vdpath (vdpath)

NOTE: When you add the libraries to the /usr/maxplus2/vwlogic/standard/viewdraw.ini file, they are automatically set when you create a new project. Powerview tools search these libraries sequentially, so it is important to add them in the order in which they are listed in Figure 1.

Table 1 shows the libraries that must be specified in the DIR statements in the viewdraw.ini file.

Table 1. Powerview Application Libraries

Library Library Alias Source Topics
alt_max2 alt_max2 Altera Graphical elements for ViewDraw
max2sim max2_sim Altera Models for project simulation
synlib altera Altera VHDL synthesis library for the MAX+PLUS® II software
alt_mf alt_mf Altera VHDL models of MAX+PLUS II logic functions
alt_vtl alt_vtl Altera VITAL-compliant primitives
builtin builtin Altera Basic primitives such as INPUT pins, OUTPUT pins, AND gates, OR gates, etc.
74ls vl74ls Viewlogic 74-series macrofunctions
vdpath vdpath Viewlogic Standard library of parameterized modules (LPM) functions

NOTE: The Altera-provided libraries must be listed before the Viewlogic-provided libraries in the viewdraw.ini file to ensure that the correct versions of the megafunctions, macrofunctions, and primitives are used.

NOTE: Go to Altera-Provided Logic & Symbol Libraries for more information on Altera-supplied libraries. Refer to the Powerview documentation for more information on setting up the viewdraw.ini file.


MAX+PLUS II/Viewlogic Powerview Project File Structure

In the MAX+PLUS® II software, a project name is the name of a top-level design file, without the filename extension. This design file can be an EDIF, Verilog HDL, or VHDL netlist file; an Altera® Hardware Description Language (AHDL) TDF; or any other MAX+PLUS II-supported design file. The EDIF netlist file must be created by Powerview and imported into the MAX+PLUS II software as an EDIF Input File (.edf). Figure 1 shows an example of MAX+PLUS II project directory structure that includes Powerview-generated files.

Figure 1. Sample MAX+PLUS II Project Organization

Sample MAX+PLUS II Project Organization

The MAX+PLUS II software stores the connectivity data on the links between design files in a hierarchical project in a Hierarchy Interconnect File (.hif), but refers to the entire project only by its project name. The MAX+PLUS II Compiler uses the HIF to build a single, fully flattened project database that integrates all the design files in a project hierarchy.

Unlike Powerview, the MAX+PLUS II software does not automatically create a project directory when you create a project. A single directory can contain several MAX+PLUS II design files, and you can specify any one of the designs in the directory as a project in the MAX+PLUS II software.

Viewlogic Powerview Local Work Area Structure

When you create a project with the Powerview Cockpit's Create command (Project menu), the project directory is created. You should generate design files and functional simulation files under this directory. A max2 subdirectory is automatically created under your current project directory when you generate an EDIF file from your schematic or VHDL file. The <project name>.edf file is stored in the max2 subdirectory. All MAX+PLUS® II Compiler output files are created in the /<project name>/max2 subdirectory.

NOTE: ViewDraw files are identified by their directories and not by their extensions, so it is easy to overwrite files unintentionally. To avoid overwriting files, Altera recommends that you create a new project directory, <project name>/max2/sim, where you can generate all the files needed for simulation.

ViewDraw Project File Structure

Each ViewDraw project directory contains three subdirectories: wir, sch, and sym. See Table 1.

Table 1. ViewDraw Subdirectories

Directory Topics
./wir Wirelist files that contain connectivity information for a particular logic block
./sch Schematics that contain logic
./sym Symbol files that are the ViewDraw graphical representation of the logic blocks

Each file type uses the filename extension .1. Different file types are distinguished only by their directory: /lib/wir/<project name>.1 is a wirelist file; /lib/sch/<project name>.1 is the corresponding schematic file; and /lib/sym/<project name>.1 is the corresponding symbol.

VHDL Project File Structure

Each VHDL project directory contains three subdirectories. See Table 2.

Table 2. VHDL Subdirectories

Directory Topics
./synth All synthesis-related files and directories
./synth/<entity> Four types of files: <entity>.pdf, <entity>.opt, <entity>.sta, and <entity>.gnl
./wir Wirelist for synthesized VHDL modules

NOTE: For each VHDL entity in the design, there is a corresponding ./synth/<entity> directory.


Altera-Provided Logic & Symbol Libraries

The MAX+PLUS® II/Viewlogic Powerview environment provides libraries for compiling, synthesizing, and simulating designs.

NOTE: You can create your own libraries of custom symbols and logic functions for use in ViewDraw schematics and VHDL design files. You can use custom symbols (and functions) to incorporate an EDIF Input File, TDF, or any other MAX+PLUS II-supported design file into a project. The MAX+PLUS II software uses the vwlogic.lmf Library Mapping File to map ViewDraw symbols to equivalent MAX+PLUS II megafunctions, macrofunctions, or primitives. To use custom symbols and functions, you can create a custom LMF that maps your custom functions to equivalent EDIF Input Files, TDFs, or other MAX+PLUS II-supported design files. Go to "Library Mapping File" and "Viewlogic Library Mapping File" in MAX+PLUS II Help for more information.

Logic symbols used in ViewDraw software are available from the MAX+PLUS II alt_max2 library, the ViewDraw builtin and 74ls libraries, and the ViewDatapath vdpath library. VHDL models of MAX+PLUS II logic functions are available from the Altera-provided alt_mf library.

The alt_max2 Library

The alt_max2 library provides MAX+PLUS II-specific logic functions that can be used to take advantage of special architectural features in each Altera® device family. See Table 1. Symbols and functional simulation models are available for all of these elements.

The alt_mf Library

The Altera-provided alt_mf library, which supports the Viewlogic Vantage VHDL Analyzer software, contains VHDL simulation models for all logic functions listed in the following table. The library is configured so that these functions pass untouched through the EDIF netlist file to the MAX+PLUS II Compiler, providing you with optimal control over design processing. Altera also provides models for all of the logic functions that you can synthesize and simulate. These models allow you to perform functional VHDL simulation while maintaining an architecture-independent VHDL description.

Table 1. Architecture Control Logic Functions

Name Note (1), Note (2) Description Name Description Name Description
8fadd 8-bit full adder macrofunction LCELL Logic cell buffer primitive EXP MAX® 5000, MAX 7000, and MAX 9000 Expander buffer primitive
8mcomp 8-bit magnitude comparator macrofunction GLOBAL Global input buffer primitive SOFT Soft buffer primitive
8count 8-bit up/down counter macrofunction CASCADE FLEX® 6000, FLEX 8000, and FLEX 10K cascade buffer primitive OPNDRN Open-drain buffer primitive
81mux 8-to-1 multiplexer macrofunction CARRY FLEX 6000, FLEX 8000, and FLEX 10K cascade buffer primitive DFFE Note (2) D-type flipflop with Clock Enable primitive
clklock Phase-locked loop megafunction        

Notes:

  1. Logic function names that begin with a number must be prefixed with "a_" in VHDL designs. For example, 8fadd must be specified as a_8fadd.
  2. For designs that are targeted to FLEX 6000 devices, you should use the DFFE primitive only if the design contains either a Clear or Preset signal, but not both. If your design contains both a Clear and a Preset signal, you must use the DFFE6K primitive.

NOTE: Choose Old-Style Macrofunctions, Primitives, or Megafunctions/LPM from the MAX+PLUS II Help menu for detailed information on these functions.

 

Go to the following topics, which are available on the web, for additional information:

  • FLEX Devices
  • MAX Devices
  • Classic Device Family


MAX+PLUS II/Viewlogic Powerview Simulation Flow

Figure 1 shows the project simulation flow for the MAX+PLUS® II/Viewlogic Powerview interface.

Figure 1. MAX+PLUS II/Viewlogic Powerview Project Simulation Flow

Altera-provided items are shown in blue.

Simulation Flow


Performing a Timing Simulation with Fusion/VCS for Powerview Software

After you have compiled a project with the MAX+PLUS® II software to generate a VHDL Output File (.vho) and a Standard Delay Format (SDF) Output File (.sdo), you can perform a timing simulation with Fusion/VCS software.

To simulate a project with Fusion/VCS software, follow these steps:

  1. Be sure to set up your working environment correctly, as described in Setting Up the MAX+PLUS II/Viewlogic Powerview Working Environment.

  2. Generate a VHDL Output File (.vdo) and an SDF ver 2.1 or 1.0 Output File (.sdo) for your project, as described in Compiling Projects with MAX+PLUS II Software.

  3. Create a new sim directory under your max2 directory to contain your Fusion/VCS simulation-related files.

  4. To use the SDF Output File with the Fusion/VCS software, create a PLI table file (.tab) in the <project name>/max2/sim directory that contains the following line:

    $sdf_annotate call=sdf_annotate_call acc=tchk, mp:<project name> ENTER

  5. Open the Fusion/VCS dialog box by choosing the max2_VCS button from the Altera® Design Tools Drawer in the Powerview Cockpit.

    1. Type <project name>/max2/<project name>.vo in the Verilog Design and Object Files box.

    2. Type <project name>.tab in the PLI Table File box.

    3. Type <project name>/max2/alt_max2.vo in the Verilog Library File 1 box.

    4. (Optional) To use a command file or to set stimuli during simulation, select the Debug option in the VCS box and type the name of the command file in the Simulation Command-file box.

      NOTE: When using a command file or setting stimuli, include the signal scope as part of the signal name. For example, to manipulate clk, a top-level signal in the fadd project, name the signal as fadd.clk.

    5. Choose OK.

Go to: Go to Performing a Timing Simulation with ViewSim Software in these MAX+PLUS II ACCESSSM Key topics for related information:


Compiling Projects with MAX+PLUS II Software

The MAX+PLUS® II Compiler can process design files in a variety of formats. This topic describes how to use MAX+PLUS II software to compile projects in which the top-level design file is an EDIF Input File (with the extension .edf).

Note: Refer to the following sources for additional information:

  • Go to MAX+PLUS II Help for information on compiling VHDL and Verilog HDL, design files directly with the MAX+PLUS II Compiler.

  • Go to Running Synopsys Compilers from MAX+PLUS II Software for information on running the Synopsys Design Compiler or FPGA Compiler software on a VHDL or Verilog HDL design from within the MAX+PLUS II Compiler window.

To compile a design (also called a "project") with MAX+PLUS II software, go through the following steps:

  1. Create design files that are compatible with the MAX+PLUS II software and convert them into EDIF Input Files with the extension .edf. Specific instructions for some tools are described in these MAX+PLUS II ACCESSSM Key Guidelines. Otherwise, refer to MAX+PLUS II Help or the product documentation for your design entry or synthesis and optimization tool.

  2. If your design files contain symbols (or HDL instantiations) representing your own custom lower-level logic functions, create a mapping for each function in a Library Mapping File (.lmf) to map the custom symbol to the corresponding EDIF Input File, AHDL Text Design File (.tdf), or other MAX+PLUS II-supported design file. These custom functions are represented in design files as hollow-body symbols or "black box" HDL descriptions.

    Note: Go to "Library Mapping Files (.lmf)" in MAX+PLUS II Help for more information.

  3. Open MAX+PLUS II and specify the name of your top-level design file as the project name with the Project Name command (File menu). If you open an HDL file in the MAX+PLUS II Text Editor, you can choose the Project Set Project to Current File command (File menu) instead.

    Note: You can also compile a project from a command line. However, the first time you compile a project, the settings you need to specify are easier to specify from within the MAX+PLUS II software. After you have run the graphical user interface for the MAX+PLUS II software at least once, you can more easily use the command-line setacf utility to modify options in the Assignment & Configuration File (.acf) for the project. Type setacf -h Enter and maxplus2 -h Enter for descriptions of setacf and MAX+PLUS II command-line syntax.

  4. Choose Device (Assign menu) and select the target Altera device family in the Device Family drop-down list box. If you wish to implement the design logic in a specific device, select it in the Devices box. Otherwise, select AUTO to allow the MAX+PLUS II Compiler to choose the best device(s) in the current device family. If your design entry or synthesis and optimization tool required you to specify a target family and/or device, specify the same information in this dialog box. For information on partitioning logic among multiple devices, go to MAX+PLUS II Help. Choose OK.

  5. Open the Compiler window by choosing the Compiler command (MAX+PLUS II menu). Go through the following steps to specify the options necessary to compile the design file(s) in your project:

    1. Ensure that all EDIF netlist files have the extension .edf and choose EDIF Netlist Reader Settings (Interfaces menu).

    2. Select a vendor name in the Vendor drop-down list box to activate the default settings for that vendor. This name should be the name of the vendor whose tool(s) you used to create the EDIF netlist files. If your vendor name does not appear, select Custom instead.

      Note: If you are compiling a design created with Synopsys FPGA Express software, select Synopsys, choose the Customize button, enter <project name>.lmf in the LMF #1 box, choose OK, and skip to step 6.

    3. If you selected an existing vendor name in the Vendor box and your project contains design files that require custom LMF mappings, choose the Customize button to expand the dialog box to show all settings. Turn on the LMF #2 checkbox and type your custom LMF's filename in the corresponding text box, or select a name from the Files box. The selection in the Vendor box will change to Custom and all settings will be retained until you change them again.

    4. If you selected Custom in the Vendor box, choose the Customize button to expand the dialog box to show all settings. Any previously defined custom settings will be displayed. Under Signal Names, type one or more names with up to 20 total name characters in the VCC or GND box if your EDIF Input File(s) use one or more names other than VCC or GND for the global high or low signals. Multiple signal names must be separated by either a comma (,) or a space. Under Library Mapping Files, turn on the LMF #1 checkbox and type a filename in the text box following it, or select a name from the Files box. If necessary, specify another LMF name in the LMF #2 box. Go to MAX+PLUS II Help for detailed information on the settings available in the EDIF Netlist Reader Settings dialog box.

    5. Choose OK.

  6. If your design files contain symbols (or HDL instantiations) representing your own custom lower-level logic functions, you may need to ensure that all files are present in your project directory, i.e., the same directory as the top-level design file. Otherwise, you must specify the directories containing these files as user libraries with the User Libraries command (Options menu).

  7. Follow all guidelines that apply to your design entry or synthesis and optimization tool:

    • Exemplar Logic Galileo Extreme-Specific Compiler Settings
    • Synopsys DesignWare-Specific Compiler Settings
    • Converting Synopsys FPGA Compiler & Design Compiler Timing Constraints into MAX+PLUS II-Compatible Format with the syn2acf Utility
    • Synplicity Synplify-Specific Compiler Settings

  8. If you wish to generate EDIF, VHDL, or Verilog HDL output files for post-compilation simulation or timing analysis with another EDA tool, go through the following steps:

    1. (Optional) Turn on the Optimize Timing SNF command (Processing menu) to reduce the size of the output file(s). Turning on this command can reduce the size of output netlists by up to 30%.

      Note: This command does not create optimized timing SNFs on UNIX workstations. However, a non-optimized timing SNF provides the same functional and timing information as an optimized timing SNF.

    2. If you wish to generate EDIF Output Files (.edo), go through these steps:

      1. Turn on the EDIF Netlist Writer command (Interfaces menu). Then choose the EDIF Netlist Writer Settings command (Interfaces menu).

      2. Select a vendor name in the Vendor drop-down list box to activate the default settings for that vendor and choose OK. If your vendor name does not appear, select Custom instead and specify the settings that are appropriate for your simulation or timing analysis tool. Go to MAX+PLUS II Help for detailed information on the options available in the EDIF Netlist Writer Settings dialog box.

      3. To generate an optional Standard Delay Format (SDF) Output File (.sdo), choose the Customize button to expand the dialog box to show all settings. Select one of the SDF Output File options under Write Delay Constructs To, and choose OK.

      The filenames of the EDIF Output File(s) and optional SDF Output File(s) are the same as the user-defined chip name(s) for the project; if no chip names exist, the Compiler assigns filenames that are based on the project name. For a multi-device project, the Compiler also generates a top-level EDIF Output File that is uniquely identified by "_t" appended to the project name. In addition, the Compiler automatically generates a VHDL Memory Model Output File, <project name>.vmo, when it generates an EDIF Output File that contains memory (RAM or ROM).

    3. If you wish to generate VHDL Output Files (.vho), turn on the VHDL Netlist Writer command (Interfaces menu). Then choose VHDL Netlist Writer Settings command (Interfaces menu). Select VHDL Output File (.vho) or one of the SDF Output File options under Write Delay Constructs To, and choose OK. SDF ver. 2.1 files contain timing delay information that allows you to perform back-annotation simulation in VHDL with VITAL-compliant simulation libraries. The VHDL Output Files generated by the Compiler have the extension .vho, but are otherwise named in the same way as the EDIF Output Files described above.

    4. If you wish to generate Verilog HDL Output Files (.vo), turn on the Verilog Netlist Writer command (Interfaces menu). Then choose Verilog Netlist Writer Settings command (Interfaces menu). Select Verilog Output File (.vo) or one of the SDF Output File options under Write Delay Constructs To, and choose OK. SDF Output Files contain timing delay information that allows you to perform back-annotation simulation in Verilog HDL. The Verilog Output Files generated by the Compiler have the extension .vo, but are otherwise named in the same way as the EDIF Output Files described above.

  9. To run the MAX+PLUS II Compiler, choose the Project Save & Compile command (File menu) or choose the Start button in the Compiler window.

    Note: See step 3 for information on running MAX+PLUS II software from the command line.

  10. Once you have compiled the project with the MAX+PLUS II Compiler, you can use the VHDL, Verilog HDL, or EDIF output file(s), and the optional SDF Output File(s) (.sdo) to perform timing analysis or timing simulation with another EDA tool. Specific instructions for some tools are described in these MAX+PLUS II ACCESS Key Guidelines. Otherwise, refer to MAX+PLUS II Help or the product documentation for your EDA tool.

The MAX+PLUS II Compiler also generates a Report File (.rpt), a Pin-Out File (.pin), and one or more of the following files for device programming or configuration:

  • JEDEC Files (.jed)
  • Programmer Object Files (.pof)
  • SRAM Object Files (.sof)
  • Hexadecimal (Intel-format) Files (.hex)
  • Tabular Text Files (.ttf)
Go to: Refer to the following sources for additional information:
  • Go to Compiler Procedures in MAX+PLUS II Help for information on other available Compiler settings.
  • Go to Programmer Procedures in MAX+PLUS II Help for instructions on creating other types of programming files and on programming or configuring Altera devices.
  • Go to Back-Annotating MAX+PLUS II Pin Assignments to Design Architect Symbols for information on back-annotating pin assignments in Mentor Graphics Design Architect schematics.
  • Go to Programming Altera Devices for information on the different programming hardware options for Altera device families.

 

Go to the following topics, which are available on the web, for additional information:

  • MAX+PLUS II Development Software
  • Altera Programming Hardware


Programming Altera Devices

Once you have successfully compiled and simulated a project with the MAX+PLUS® II software, you can program an Altera® device and test it in the target circuit. Figure 1 shows the device programming flow for MAX+PLUS II software.

Figure 1. MAX+PLUS II Device Programming Flow

Altera-provided items are shown in blue.

Figure 1

You can program devices with Altera programming hardware and MAX+PLUS II Programmer software installed on a 486- or Pentium-based PC or a UNIX workstation, or with programming hardware and software available from other manufacturers. Table 1 shows the available Altera programming hardware options on PCs and UNIX workstations.

Table 1. Altera Programming Hardware
Programming
Hardware
Option
PCs
UNIX
Work-
stations
ACEX® 1K
Devices
MAX® 3000A
Devices
Classic®
&
MAX 5000
Devices
MAX 7000
&
MAX 7000E
Devices

MAX 7000A,
MAX 7000AE,
MAX 7000B,
MAX 7000S
MAX 9000
&
MAX 9000A
Devices

FLEX® 6000,
FLEX 6000A,
FLEX 8000,
FLEX 10K,
FLEX 10KA,
FLEX 10KB,
&
FLEX 10KE Devices
In-System
Programming/
Configuration
Logic Programmer
card, PL-MPU
Master
Programming
Unit, and
device-specific
adapters
Step:
   
Step:
Step:
Step:
Step:
   
BitBlaster
Download Cable
Step:
Step:
Step:
Step:
   
Step:
Step:
Step:
ByteBlasterMV
Download Cable
Step:
 
Step:
Step:
   
Step:
Step:
Step:
MasterBlaster Download Cable
Step:
Step:
Step:
Step:
   
Step:
Step:
Step:

If you wish to transfer programming files from a UNIX workstation to a PC over a network with File Transfer Protocol (FTP) or other similar transfer programs, be sure to select binary transfer mode.

Programming hardware from other manufacturers varies, but typically consists of a device connected to one of the serial ports on the workstation. Various vendors, such as Data I/O and BP Microsystems, supply hardware and software for programming Altera devices.

Go to: Go to Compiling Projects with MAX+PLUS II Software for information on creating programming files.

 

Go to the following topics, which are available on the web, for additional information:

  • MAX+PLUS II Development Software
  • Altera Programming Hardware
  • FLEX Devices
  • MAX Devices
  • Classic Device Family

Last Updated: August 28, 2000 for MAX+PLUS II version 10.0
border line
| Home | List by Vendor | List by Tool | List by Function | Viewlogic Topics | Fusion/VCS Topics |
Documentation Conventions

Copyright © 1995-2000 Altera Corporation, 101 Innovation Drive, San Jose, California 95134, USA. All rights reserved. By accessing any information on this CD-ROM, you agree to be bound by the terms of Altera's Legal Notice.