- •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
Writing Circuit Descriptions
Y <= A + B + C;
Z <= D + A + B;
The parser does not recognize A + B as a common subexpression, because it parses the second equation as (D + A) + B. You can force the parser to recognize the common subexpression by rewriting the second assignment statement as follows.
Z <= A + B + D;
or
Z <= D + (A + B);
Note: You do not have to rewrite the assignment statement, because Foundation Express recognizes common subexpressions automatically.
Changing an Operator Bit-Width
The adder in the following example sums the 8-bit value of A (a
BYTE) with the 8-bit value of TEMP. TEMP’s value is either B, which is used only when it is less than 16, or C, which is a 4-bit value (a NIBBLE).Therefore, the upper four bits of TEMP are always 0. Foundation Express cannot derive this fact, because TEMP is declared with type BYTE.
You can simplify the synthesized circuit by changing the declared type of TEMP to NIBBLE (a 4-bit value). With this modification, half adders, rather than full adders, are required to implement the top four bits of the adder circuit, which figure, “Function with One Adder Schematic,” illustrates.
function ADD_IT_16 (A, B: BYTE; C: NIBBLE) return BYTE is variable TEMP: BYTE;
begin
if B < 16 then TEMP <= B;
else
TEMP <= C; end if;
return A + TEMP; end;
VHDL Reference Guide |
8-11 |
VHDL Reference Guide
Figure 8-10 Function With One Adder Schematic
The following example shows how this change in TEMP’s declaration can yield a significant savings in circuit area, which the figure following the example illustrates.
function |
ADD_IT_16 (A, B: BYTE; C: NIBBLE) |
|
return BYTE is |
|
|
variable TEMP: NIBBLE; |
-- Now only 4 bits |
|
begin |
|
|
if B < |
16 then |
|
TEMP |
<= NIBBLE(B); |
-- Cast BYTE to NIBBLE |
else |
|
|
TEMP |
<= C; |
|
end if; |
|
|
return |
A + TEMP; |
-- Single adder |
end; |
|
|
8-12 |
Xilinx Development System |
Writing Circuit Descriptions
Figure 8-11 Using TEMP Declaration to Save Circuit Area
Using State Information
You can also apply design knowledge in sequential designs. Often you can make strong assertions about the value of a signal in a particular state of a finite-state machine. You can describe this information to Foundation Express. The following example shows the VHDL description of a simple state machine that uses two processes.
package STATES is
type STATE_TYPE is (SET0, HOLD0, SET1); end STATES;
use work.STATES.all;
entity MACHINE is port(X, CLOCK: in BIT;
CURRENT_STATE: buffer STATE_TYPE; Z: buffer BIT);
end MACHINE;
VHDL Reference Guide |
8-13 |
VHDL Reference Guide
architecture BEHAVIOR of MACHINE is signal NEXT_STATE: STATE_TYPE; signal PREVIOUS_Z: BIT;begin
-- Process to hold combinatorial logic. COMBIN: process(CURRENT_STATE, X, PREVIOUS_Z)
begin |
|
|
case CURRENT_STATE is |
|
|
when SET0 => |
|
|
|
Z <= ’0’; |
-- Set Z to ’0’ |
|
NEXT_STATE <= HOLD0; |
|
when HOLD0 => |
|
|
|
Z <= PREVIOUS_Z; |
-- Hold value of Z |
|
if X = ’0’ then |
|
|
NEXT_STATE <= HOLD0; |
|
|
else |
|
|
NEXT_STATE <= SET1; |
|
|
end if; |
|
when SET1 => |
-- Set Z to ’1’ |
|
|
Z <= ’1’; |
|
|
NEXT_STATE <= SET0; |
|
end |
case; |
|
end process COMBIN; |
|
|
-- Process to hold synchronous elements (flipflops).
SYNCH: process begin
wait until CLOCK’event and CLOCK = ’1’; CURRENT_STATE <= NEXT_STATE; PREVIOUS_Z <= Z;
end process SYNCH; end BEHAVIOR;
8-14 |
Xilinx Development System |
Writing Circuit Descriptions
Figure 8-12 Schematic of Simple State Machine with Two Processes
The following figure shows a schematic of a simple state machine with two processes.In the state hold0, the output Z retains its value from the previous state. To accomplish this, you insert a flip-flop to hold the PREVIOUS_Z. However, you can make some assertions about the value of Z. In state HOLD0, the value of Z is always 0. You can deduce this from the fact that the state HOLD0 is entered only from the state SET0, where Z is always assigned ‘0.’
The following example shows how you can change the VHDL description to use this assertion, resulting in a simpler circuit. The figure following the example illustrates the circuit.
package STATES is
type STATE_TYPE is (SET0, HOLD0, SET1); end STATES;
use work.STATES.all;
entity MACHINE is port(X, CLOCK: in BIT;
CURRENT_STATE: buffer STATE_TYPE; Z: buffer BIT);
end MACHINE;
architecture BEHAVIOR of MACHINE is signal NEXT_STATE: STATE_TYPE;
begin
-- Combinatorial logic.
COMBIN: process(CURRENT_STATE, X)
VHDL Reference Guide |
8-15 |
VHDL Reference Guide
begin |
|
|
case CURRENT_STATE is |
|
|
when SET0 => |
|
|
|
Z <= ’0’; |
-- Set Z to ’0’ |
|
NEXT_STATE <= HOLD0; |
|
when HOLD0 => |
|
|
|
Z <= ’0’; |
-- Hold Z at ’0’ |
|
if X = ’0’ then |
|
|
NEXT_STATE <= HOLD0; |
|
|
else |
|
|
NEXT_STATE <= SET1; |
|
|
end if; |
|
when SET1 => |
-- Set Z to ’1’ |
|
|
Z <= ’1’; |
|
|
NEXT_STATE <= SET0; |
|
end |
case; |
|
end process COMBIN;
-- Process to hold synchronous elements (flip-flops) SYNCH: process
begin
wait until CLOCK’event and CLOCK = ’1’; CURRENT_STATE <= NEXT_STATE;
end process SYNCH; end BEHAVIOR;
Figure 8-13 Schematic of an Improved State Machine
8-16 |
Xilinx Development System |
