- •About This Manual
- •Additional Resources
- •Manual Contents
- •Conventions
- •Typographical
- •Online Document
- •Using Foundation Express with VHDL
- •Hardware Description Languages
- •Typical Uses for HDLs
- •Advantages of HDLs
- •About VHDL
- •Foundation Express Design Process
- •Using Foundation Express to Compile a VHDL Design
- •Design Methodology
- •Design Descriptions
- •Entities
- •Entity Generic Specifications
- •Entity Port Specifications
- •Architecture
- •Declarations
- •Components
- •Concurrent Statements
- •Constant Declarations
- •Processes
- •Signal Declarations
- •Subprograms
- •Type Declarations
- •Examples of Architectures for NAND2 Entity
- •Configurations
- •Packages
- •Using a Package
- •Package Structure
- •Package Declarations
- •Package Body
- •Resolution Functions
- •Data Types
- •Type Overview
- •Enumeration Types
- •Enumeration Overloading
- •Enumeration Encoding
- •Enumeration Encoding Values
- •Integer Types
- •Array Types
- •Constrained Array
- •Unconstrained Array
- •Array Attributes
- •Record Types
- •Record Aggregates
- •Predefined VHDL Data Types
- •Data Type BOOLEAN
- •Data Type BIT
- •Data Type CHARACTER
- •Data Type INTEGER
- •Data Type NATURAL
- •Data Type POSITIVE
- •Data Type STRING
- •Data Type BIT_VECTOR
- •Unsupported Data Types
- •Physical Types
- •Floating-Point Types
- •Access Types
- •File Types
- •Express Data Types
- •Subtypes
- •Expressions
- •Overview
- •Operators
- •Logical Operators
- •Relational Operators
- •Adding Operators
- •Unary (Signed) Operators
- •Multiplying Operators
- •Miscellaneous Arithmetic Operators
- •Operands
- •Operand Bit-Width
- •Computable Operands
- •Aggregates
- •Attributes
- •Expressions
- •Function Calls
- •Identifiers
- •Indexed Names
- •Literals
- •Numeric Literals
- •Character Literals
- •Enumeration Literals
- •String Literals
- •Qualified Expressions
- •Records and Fields
- •Slice Names
- •Limitations on Null Slices
- •Limitations on Noncomputable Slices
- •Type Conversions
- •Sequential Statements
- •Assignment Statements and Targets
- •Simple Name Targets
- •Indexed Name Targets
- •Slice Targets
- •Field Targets
- •Aggregate Targets
- •Variable Assignment Statements
- •Signal Assignment Statements
- •Variable Assignment
- •Signal Assignment
- •if Statements
- •Evaluating Conditions
- •Using the if Statement to Infer Registers and Latches
- •case Statements
- •Using Different Expression Types
- •Invalid case Statements
- •loop Statements
- •Basic loop Statement
- •while...loop Statements
- •for...loop Statements
- •Steps in the Execution of a for...loop Statement
- •for...loop Statements and Arrays
- •next Statements
- •exit Statements
- •Subprograms
- •Subprogram Always a Combinatorial Circuit
- •Subprogram Declaration and Body
- •Subprogram Calls
- •Procedure Calls
- •Function Calls
- •return Statements
- •Procedures and Functions as Design Components
- •Example with Component Implication Directives
- •Example without Component Implication Directives
- •wait Statements
- •Inferring Synchronous Logic
- •Combinatorial Versus Sequential Processes
- •null Statements
- •Concurrent Statements
- •Overview
- •process Statements
- •Combinatorial Process Example
- •Sequential Process Example
- •Driving Signals
- •block Statements
- •Nested Blocks
- •Guarded Blocks
- •Concurrent Versions of Sequential Statements
- •Concurrent Procedure Calls
- •Concurrent Signal Assignments
- •Simple Concurrent Signal Assignments
- •Conditional Signal Assignments
- •Selected Signal Assignments
- •Component Instantiation Statements
- •Direct Instantiation
- •generate Statements
- •for...generate Statements
- •Steps in the Execution of a for...generate Statement
- •Common Usage of a for...generate Statement
- •if...generate Statements
- •Register and Three-State Inference
- •Register Inference
- •The Inference Report
- •Latch Inference Warnings
- •Controlling Register Inference
- •Inferring Latches
- •Inferring Set/Reset (SR) Latches
- •Inferring D Latches
- •Inferring Master-Slave Latches
- •Inferring Flip-Flops
- •Inferring D Flip-Flops
- •Inferring JK Flip-Flops
- •Inferring Toggle Flip-Flops
- •Getting the Best Results
- •Understanding Limitations of Register Inference
- •Three-State Inference
- •Reporting Three-State Inference
- •Controlling Three-State Inference
- •Inferring Three-State Drivers
- •Inferring a Simple Three-State Driver
- •Three-State Driver with Registered Enable
- •Three-State Driver Without Registered Enable
- •Writing Circuit Descriptions
- •How Statements Are Mapped to Logic
- •Design Structure
- •Adding Structure
- •Using Variables and Signals
- •Using Parentheses
- •Using Design Knowledge
- •Optimizing Arithmetic Expressions
- •Arranging Expression Trees for Minimum Delay
- •Sharing Common Subexpressions
- •Changing an Operator Bit-Width
- •Using State Information
- •Propagating Constants
- •Sharing Complex Operators
- •Asynchronous Designs
- •Don’t Care Inference
- •Using Don’t Care Default Values
- •Differences Between Simulation and Synthesis
- •Synthesis Issues
- •Feedback Paths and Latches
- •Fully Specified Variables
- •Asynchronous Behavior
- •Understanding Superset Issues and Error Checking
- •Foundation Express Directives
- •Notation for Foundation Express Directives
- •Foundation Express Directives
- •Translation Stop and Start Pragma Directives
- •synthesis_off and synthesis_on Directives
- •Resolution Function Directives
- •Component Implication Directives
- •Foundation Express Packages
- •std_logic_1164 Package
- •std_logic_arith Package
- •Using the Package
- •Modifying the Package
- •Data Types
- •UNSIGNED
- •SIGNED
- •Conversion Functions
- •Arithmetic Functions
- •Example 10-1: Binary Arithmetic Functions
- •Example 10-2: Unary Arithmetic Functions
- •Comparison Functions
- •Example 10-3: Ordering Functions
- •Example 10-4: Equality Functions
- •Shift Functions
- •ENUM_ENCODING Attribute
- •pragma built_in
- •Type Conversion
- •numeric_std Package
- •Understanding the Limitations of numeric_std package
- •Using the Package
- •Data Types
- •Conversion Functions
- •Resize Function
- •Arithmetic Functions
- •Comparison Functions
- •Defining Logical Operators Functions
- •Shift Functions
- •Rotate Functions
- •Shift and Rotate Operators
- •std_logic_misc Package
- •ATTRIBUTES Package
- •VHDL Constructs
- •VHDL Construct Support
- •Design Units
- •Data Types
- •Declarations
- •Specifications
- •Names
- •Identifiers and Extended Identifiers
- •Specifics of Identifiers
- •Specifics of Extended Identifiers
- •Operators
- •Shift and Rotate Operators
- •xnor Operator
- •Operands and Expressions
- •Sequential Statements
- •Concurrent Statements
- •Predefined Language Environment
- •VHDL Reserved Words
- •Examples
- •Moore Machine
- •Mealy Machine
- •Read-Only Memory
- •Waveform Generator
- •Smart Waveform Generator
- •Definable-Width Adder-Subtracter
- •Count Zeros—Combinatorial Version
- •Count Zeros—Sequential Version
- •Soft Drink Machine—State Machine Version
- •Soft Drink Machine—Count Nickels Version
- •Carry-Lookahead Adder
- •Carry Value Computations
- •Implementation
- •Serial-to-Parallel Converter—Counting Bits
- •Input Format
- •Implementation Details
- •Serial-to-Parallel Converter—Shifting Bits
- •Programmable Logic Arrays
Chapter 5
Sequential Statements
Foundation Express interprets sequential statements, such as A:= 3, in the order in which they appear in code. VHDL sequential statements can appear only in processes and subprograms.
This chapter describes and illustrates the different types of sequential statements in the following sections.
•“Assignment Statements and Targets”
•“Variable Assignment Statements”
•“Signal Assignment Statements”
•“if Statements”
•“case Statements”
•“loop Statements”
•“next Statements”
•“exit Statements”
•“Subprograms”
•“return Statements”
•“wait Statements”
•“null Statements”
Assignment Statements and Targets
Use an assignment statement to assign a value to a variable or signal. The syntax follows.
target := expression; -- Variable assignment target <= expression; -- Signal assignment
VHDL Reference Guide |
5-1 |
VHDL Reference Guide
target is a variable or signal (or part of a variable or signal, such as a subarray) that receives the value of the expression. The expression must evaluate to the same type as the target. See the “Expressions” section of the “Expressions” chapter for more information.
There are five kinds of targets.
•Simple names, such as my_var
•Indexed names, such as my_array_var(3)
•Slices, such as my_array_var(3 to 6)
•Field names, such as my_record.a_field
•Aggregates, such as (my_var1, my_var2)
The difference in syntax between variable assignments and signal assignments follows.
•Variables use the := operator.
Variables are local to a process or subprogram, and their assignments take effect immediately.
•Signals use the <= operator.
Signals need to be global in a process or subprogram, and their assignments take effect at the end of a process. Signals are the only means of communication between processes. For more information on semantic differences, see the “Signal Assignment” section of this chapter.
Simple Name Targets
The syntax for an assignment to a simple name (identifier) target follows.
identifier := expression; -- Variable assignment identifier <= expression; -- Signal assignment
identifier is the name of a signal or variable. The assigned expression must have the same type as the signal or variable. For array types, all elements of the array are assigned values.
The following example shows assignments to simple name targets.
variable A, B: BIT;
signal |
C: |
BIT_VECTOR(1 to 4); |
5-2 |
Xilinx Development System |
Sequential Statements
-- Target |
|
Expression |
|
|
|
|
|
A |
:= |
’1’; |
-- Variable |
A |
is assigned |
’1’ |
|
B |
:= |
’0’; |
-- |
Variable |
B |
is assigned |
’0’ |
C<= “1100"; -- Signal array C is assigned
--bit value “1100"
Indexed Name Targets
The syntax for an assignment to an indexed name (identifier) target follows.
identifier(index_expression) := expression; |
-- Variable assignment |
identifier(index_expression) <= expression; |
-- Signal assignment |
identifier is the name of an array type signal or variable. |
|
index_expression must evaluate to an index value for the identifier |
|
array’s index type and bounds but does not have to be computable |
|
(see the “Expressions” chapter), but more hardware is synthesized if |
|
it is not. |
|
The assigned expression must contain the array’s element type. |
|
In the following example, the elements for array variable A are |
|
assigned values as indexed names. |
|
variable A: BIT_VECTOR(1 to 4);
-- Target |
|
Expression; |
||
A(1) |
:= ’1’; |
-- Assigns ’1’ to the first element of array A. |
||
A(2) |
:= ’1’; |
-- Assigns ’1’ to the second element of array A. |
||
A(3) |
:= |
’0’; |
-- |
Assigns ’0’ to the third element of array A. |
A(4) |
:= |
’0’; |
-- |
Assigns ’0’ to the fourth element of array A. |
The example below shows two indexed name targets. One of the targets is computable, and the other is not. The figure following the example illustrates the corresponding design.
entity example5 3 is port (
signal A, B: BIT_VECTOR(0 to 3); signal I: INTEGER range 0 to 3; signal Y, Z: BIT;
);
end example5 3;
architecture behave of example5 3 is
VHDL Reference Guide |
5-3 |
VHDL Reference Guide
begin
process (I, Y, Z) begin
A<= “0000";
B<= “0000";
A(I) <= Y; -- Noncomputable index expression
B(3) <= Z; -- Computable index expression
|
end process; |
|
|
end behave |
|
Y |
AN3 |
A[0] |
|
|
|
I[1] |
IV |
|
AN3 |
A[1] |
|
|
IV |
|
I[0] |
AN3 |
A[2] |
|
AN3 |
A[3] |
|
logic_0 |
B[2] |
|
|
|
|
|
B[1] |
|
|
B[0] |
Z 
B[3]
X8627
Figure 5-1 Design Illustrating Indexed Name Targets
Slice Targets
The syntax for an assignment to a slice target follows.
identifier(index_expr_1 direction index_expr_2)
identifier is the name of an array type signal or variable. Each index_expr expression must evaluate to an index value for the identifier array’s index type and bounds. Both index_expr expressions
5-4 |
Xilinx Development System |
