- •Preface
- •About This Manual
- •Other Information Sources
- •Syntax Conventions
- •Text Command Syntax
- •About the Graphical User Interface
- •Using Menus
- •Using Forms
- •HDL Synthesis Overview
- •HDL Synthesis Flow
- •Read Technology Libraries
- •Read Design Data
- •Build Generic Design
- •Save Generic Netlist
- •Synthesizing Mixed VHDL/Verilog Designs
- •Querying the HDL Design Pool
- •Using get_hdl_top_level Command
- •Using get_hdl_hierarchy Command
- •Using get_hdl_type Command
- •Building Generic Netlists from HDL
- •Multiple Top-Level Designs
- •Building Parameterized Designs
- •Verilog Modeling Styles
- •Modeling Combinational Logic
- •Register Inferencing
- •Latch Inference
- •Flip-Flop Inference
- •case Statements
- •Incomplete case Statement
- •Complete case Statement
- •Use of casex and casez Statements
- •for Statement
- •Synthesis Directives
- •Code Selection Directives
- •Architecture Selection Directive
- •case Statement Directives
- •Module Template Directive
- •Function and Task Mapping Directives
- •Set and Reset Synthesis Directives
- •Verilog Preprocessor Directives
- •Compiler Directives
- •The ‘for Compiler Directive
- •The ‘if Compiler Directive
- •The ‘eval Compiler Directive
- •The ‘{} Compiler Directive
- •Command Line Options
- •VPP Flag Attribute
- •Verilog-Related Commands and Globals
- •VHDL Modeling Style
- •Modeling Combinational Logic
- •Register Inferencing
- •Latch Inference
- •Flip-Flop Inferencing
- •Specifying Clock Edges
- •case Statement
- •Incomplete case Statement
- •Complete case Statement
- •for loop
- •Synthesis Directives
- •Code Selection Directives
- •Architecture Selection Directive
- •case Statement Directive
- •Enumeration Encoding Directive
- •Entity Template Directive
- •Function and Procedure Mapping Directives
- •Signed Type Directive
- •Resolution Function Directives
- •Type Conversion Directives
- •Set and Reset Synthesis Directives
- •Reading VHDL Designs
- •Using Arithmetic Packages From Other Vendors
- •Switching between VHDL’87 / VHDL’93
- •Reusing Previously Analyzed Entities
- •Modifying Case of VHDL Names
- •Writing VHDL Netlists
- •Selecting Bit-Level Representation
- •Selecting Between VHDL’87 and VHDL’93
- •Referring to VHDL Packages in Netlists
- •Writing Component Declarations
- •Hierarchical VHDL Designs
- •Component Instantiations and Bindings
- •Restrictions on Entities with Multiple Architectures
- •Precedence Rules for Architecture Selection
- •VHDL-Related Commands and Globals
- •Finite State Machine Overview
- •BuildGates Synthesis and Finite State Machines
- •Extracting the State Transition Table for the FSM
- •Viewing the State Transition Table for the FSM
- •FSM Optimization Features
- •Unreachable State Removal
- •State Assignment or Re-Encoding
- •State Minimization
- •Terminal State Check
- •Verilog and VHDL FSM Directives
- •Verilog FSM Directives
- •VHDL FSM Directives
- •FSM Coding Styles
- •Using the -reachable Option
- •Avoiding a Simulation Mismatch
- •EDIF Interface
- •Reading EDIF Designs
- •Writing EDIF Designs
- •Representing Power and Ground in EDIF
- •Net Representation for Power and Ground
- •Port Representation for Power and Ground
- •Instance Representation for Power and Ground
- •Verilog Constructs
- •Fully Supported Constructs
- •Declarations
- •Operators and Expressions
- •Partially Supported Constructs
- •Ignored Constructs
- •Unsupported Constructs
- •Summary of Verilog Constructs
- •VHDL Constructs
- •Notes on Supported Constructs
Envisia HDL Modeling Reference
Verilog Constructs
Fully Supported Constructs
Fully supported constructs can be used unconditionally in describing a model. These include the basic module declaration, instantiation, use of reg and wire data types, continuous assignments, always procedural block, and many of the procedural statements.
Declarations
The following module, task, function, and data type declarations are fully supported.
■module, macromodule declarations
■function, endfunction
■task, endtask
■input, output, inout port declaration, memory
■wire, wand, wor, tri, triand, trior, supply0, supply1
■integer, reg
■parameter
■local variables
Operators and Expressions
Table A-1 lists the fully supported operators (and expressions comprised of these operators with legal operands).
Table A-1 Operators and Expressions
Expressions |
Operators |
|
|
+, - |
Arithmetic operators |
|
|
==,!=,>,<, £, >= |
Comparison operators |
|
|
!, &&, ||, ~, &, |, |
Logical operators |
^, ^~, ~^, ~&, ~|, +, |
|
- , <, >, <=, >=, ==, |
|
!=, * |
|
|
|
September 2000 |
120 |
Product Version 4.0 |
Envisia HDL Modeling Reference
Verilog Constructs
Table A-1 Operators and Expressions, continued
Expressions |
Operators |
|
|
and, nand, or, nor, |
Built-in primitives |
xor, xnor, buf, not, |
|
bufif0, bufif1, tran |
|
notif0, notif1 |
|
|
|
~, - |
1’s complement/invert, 2’s |
|
complement |
|
|
&, |, ^, ^~, ~^ |
Binary Operators |
|
|
&, |, ^, ~^, ^~, ~&, |
Reduction operators |
~| |
|
|
|
>>, << |
shift operators |
|
|
{}, {n{}} |
concatenation and replication |
|
operators |
|
|
?: |
conditional operator |
|
|
Legal operands include:
■reg, integer and wire data types
■Parameters
■On wire and reg, for bit-select and for part-select in cases of constant MSB and LSB specifiers
■Sized and unsized constants in b, o, d, h bases (both unsigned and signed, as indicated by an upper or lower case “s,” for example: 4’sb1010)
■Signed constant (s or S)
■Use of x, z, ? in constants
Structural Statements
The following structural statements are fully supported.
■assign—continuous assignments
■module instantiation—named and ordered port connections
■parameter override—on module instantiation
September 2000 |
121 |
Product Version 4.0 |