Example package ee530 is

constant maxint: integer := 16#ffff#;

VHDL MINI-REFERENCE entity and_gate is
port(
type arith_mode_type is (signed, unsigned);
function minimum(constant a, b : in integer) return integer;
a,b : in std_ulogic; end ee530;
Reduced markdown conversion of https://www.ics.uci.edu/~jmoorkan/vhdlref/vhdl.html c : out std_ulogic);
generic (gate_delay: time := 5ns);
end and_gate; Package body format
PRIMARY DESIGN UNIT MODEL package body <name> is

STRUCTURE Architecture ... exported subprogram bodies

... other internally-used declarations
end <name>;
An architecture defines one particular implementation of a design unit, at some desired
Each VHDL design unit comprises an entity declaration and one or more level of abstraction.
architecture s. Each architecture defines a different implementation or model of a given Example
design unit. The entity definition defines the inputs to, and outputs from the module, and architecture <name> of <entity> is
any generic parameters used by the different implementations of the module. <declarations> package body ee530 is
begin function minimum (constant a,b : integer) return integer is
<concurrent statements> variable c : integer; -- local variable
begin
Entity Declaration Format end;
if a < b then
c := a; -- a is min
Declarations include data types, constants, signals, files, components, attributes, else
entity <name> is
subprograms, and other information to be used in the implementation description. c := b; -- b is min
port( <port definition list> ); -- input/output signal ports
end if;
generic( <generic list> ); -- optional generic list Concurrent statements describe a design unit at one or more levels of modeling
return c; -- return min value
end <name>; abstraction, including dataflow, structure, and/or behavior. end;
end ee530;
Port declaration format: <port name>: <mode> <data type>; Behavioral Model: No structure or technology implied. Usually written in sequential,
procedural style.
in : can be read but not updated within the module, carrying information into the
Dataflow Model: All datapaths shown, plus all control signals.
Package Visibility
module. (An in -port cannot appear on the left hand side of a signal assignment.) Structural Model: Interconnection of components. To make all items of a package “visible” to a design unit, precede the desired design unit
out : can be updated but not read within the module, carrying information out of the
with a use statement:
module. (An out -port cannot appear on the right hand side of a signal assigment.)
buffer : likewise carries information out of a module, but can be both updated and VHDL PACKAGES Example
read within the module.
inout : is bidirectional and can be both read and updated, with multiple update use <library name>.<package name>.all
A VHDL package contains subprograms, constant definitions, and/or type definitions to be
sources possible.
used throughout one or more design units. Each package comprises a declaration section,
A use statement may precede the declaration of any entity or architecture which is to
NOTE: A buffer is strictly an output port, i.e. can only be driven from within the in which the available (i.e. exportable) subprograms, constants, and types are declared,
utilize items from the package. If the use statement precedes the entity declaration, the
module, while inout is truly bidirectional with drivers both within and external to the and a package body, in which the subprogram implementations are defined, along with
package is also visible to the architecture.
module. any internally-used constants and types. The declaration section represents the portion of
the package that is visible to the user of that package. The actual implementations of
Example subroutines in the package are typically not of interest to the users of those subroutines. User-Developed Packages
Compile user-developed packages in your current working library. To make it visible:
entity counter is Package declaration format
port (
Incr, Load, Clock : in std_ulogic; use <package name>.all;
Carry : out std_ulogic; package <name> is
Data_Out : buffer std_ulogic_vector(7 downto 0); ... exported constant declarations
... exported type declarations
Note: std and work (your current working library) are the two default libraries. The
Data_In : in std_ulogic_vector(7 downto 0));
end counter; ... exported subprogram declarations VHDL library statement is needed to make the ieee library and/or additional
end <name>; libraries visible.
Generics allow static information to be communicated to a block from its environment for
all architectures of a design unit. These include timing information (setup, hold, delay Example Example
times), part sizes, and other parameters.
 library <lib name>; -- make library visible Arithmetic and Logical Expressions (From package: ieee.std_logic_1164.all)
use <lib name>.<pkg name>.all; -- make package visible
Expressions in VHDL are similar to those of most high-level languages. Data elements std_ulogic_vector : array (natural range <>) of std_ulogic

must be of the type, or subtypes of the same base type. Operators include the following: std_logic_vector : array (natural range <>) of std_logic
VHDL Standard Packages
Logical: and , or , nand , nor , xor , not (for boolean or bit ops) Examples
To make TEXTIO visible: use std.textio.all;
Relational: = , /= , < , <= , > , >=
Arithmetic: + , - , * , / , mod , rem , ** (exponential), abs signal dbus: bit_vector(15 downto 0);
IEEE Standard 1164 Package Concatenate: &
dbus (7 downto 4) <= "0000"; (4-bit slice of dbus)
signal cnt: std_ulogic_vector(1 to 3);
This package contained in the ieee library supports multi-valued logic signals with type variable message: string(0 to 20);
Examples
declarations and functions. To make visible:

a <= b nand c; User-Defined Enumeration Types

library ieee; -- VHDL Library stmt d := g1 * g2 / 3;
use ieee.std_logic_1164.all; Bus_16 <= Bus1_8 & Bus2_8; An enumerated data type can be created by explicitely listing all possible values.

Example
VHDL IDENTIFIERS, NUMBERS, STRINGS, AND VHDL DATA TYPES
EXPRESSIONS type opcodes is (add, sub, jump, call);
signal instruc : opcodes;
-- Type with 4 values
-- Signal of this type
Each VHDL objects must be classified as being of a specific data type. VHDL includes a
number of predefined data types, and allows users to define custom data types as ...
Identifiers needed.
if instruc = add then -- test for value 'add'
Identifiers in VHDL must begin with a letter, and may comprise any combination of letters, ...
digits, and underscores. Note that VHDL internally converts all characters to UPPER CASE . Predefined Scalar Data Types (single objects)

Examples VHDL Standard Other user-defined types

bit : 0 , 1 Custom data types can include arrays, constrained and unconstrained, and record
Memory1, Adder_Module, Bus_16_Bit
boolean : TRUE , FALSE structures.
integer : -(231) to +(231 - 1) (SUN Limit)
Numeric Constants Constrained array: Upper and lower indexes are specified.
natural : 0 to integer'high (subtype of integer)
Unconstrained array: Indexes are specified when a signal or variable of that type is
positive : 1 to integer'high (subtype of integer)
Numeric contants can be defined, and can be of any base (default is decimal). Numbers declared.
character : ASCII characters (eg. ‘ A ’)
may include embedded underscores to improve readability. Subtype: A selected subset of values of a given type. Elements of different subtypes
time (include units; eg. 10ns, 20us)
having the same base type may be combined in expressions (elements of different
Format: base#digits# (base must be a decimal number)
IEEE Standard 1164 (package ieee.std_logic_1164.all ) types cannot). Subtypes can be used to detect out-of-range values during simulation.
Examples
std_ulogic : U , X , 1 , 0 , Z , W , H , L , -
Aliases
std_logic : resolved std_ulogic values
16#9fba# (hexadecimal)
2#1111_1101_1011# (binary) X01 : subtype { X , 0 , 1 } of std_ulogic An alias defines an alternate name for a signal or part of a signal. Aliases are often
16#f.1f#E+2 (floating-point, exponent is decimal) X01Z : subtype { X , 0 , 1 , Z } of std_ulogic used to refer to selected slices of a bit_vector.
UX01 : subtype { U , X , 0 , 1 } of std_ulogic
UX01Z : subtype { U , X , 0 , 1 , Z } of std_ulogic Example
Bit String Literals
Bit vector constants are are specified as literal strings. signal instruction: bit_vector(31 downto 0);
Predefined VHDL Aggregate Data Types alias opcode: bit_vector(6 downto 0) is instruction(31 downto 25);
...
Examples bit_vector : array (natural range <>) of bit opcode <= "1010101"; -- Set the opcode part of an instruction code
string : array (natural range <>) of char
x"ffe" (12-bit hexadecimal value) text : file of string
o"777" (9-bit octal value)
b"1111_1101_1101" (12-bit binary value)
VHDL OBJECTS: CONSTANTS, VARIABLES,
IEEE Standard 1164 Aggregate Data Types AND SIGNALS
Constants 20ns 1 signal x The resolved value is 1 since 1 overrides a Z (floating) value. If the two values had
been 1 and 0 , the resolved value would have been X , indicating an unknown result.
A constant associates a value to a symbol of a given data type. The use of constants may Event Values
improve the readability of VHDL code and reduce the likelihood of making errors. The Times
declaration syntax is:
CONCURRENT STATEMENTS
NOTE: If no delay is specified, the signal event is scheduled for one infinitessimally-

Examples small delta delay from the current time. The signal change will occur in the next Concurrent statements are included within architecture definitions and within block
simulation cycle. statements, representing concurrent behavior within the modelled design unit. These
constant Vcc : signal := '1'; -- logic 1 constant statements are executed in an asynchronous manner, with no defined order, modeling the
constant zero4 : bit_vector(0 to 3) := ('0','0','0','0'); Examples behavior of independent hardware elements within a system.
(Assume current time is T)
Variables Concurrent Signal Assignment
clock <= not clock after 10ns; -- change at T + 10ns
A variable is declared within a blocks, process, procedure, or function, and is updated databus <= mem1 and mem2 after delay; -- change at T + delay A signal assignment statement represents a process that assigns values to signals. It has
immediately when an assignment statement is executed. A variable can be of any scalar or x <= '1'; -- change to '1' at time T + "delta"; three basic formats.
aggregate data type, and is utilized primarily in behavioral descriptions. It can optionally be
Element delay models may be specified as either inertial or transport. Inertial delay is the 1.
assigned initial values (done only once prior to simulation). The declaration syntax is:
default, and should be used in most cases.
A <= B;
Examples
Inertial delay: The addition to an event queue of an event scheduled at time T
process automatically cancels any events in the queue scheduled to occur prior to time T, 2.
variable count : integer := 0; i.e. any event shorter than the delay time is suppressed.
variable rega : bit_vector(7 downto 0); A <= B when <condition1> else
Transport delay: Each new event is simply inserted into the event queue,
begin C when <condition2> else
... i.e. behavior is that of a delay line. The keyword transport is used to indicate
D when <condition3> else E;
count := 7; -- assign values to variables transport delays.
rega := x"01";
... 3.
end;
Examples
with <expression> select A <=
B <= A after 5ns; -- inertial delay
B when choice1,
Signals C <= transport A after 5 ns; -- transport delay
C when choice2,
5______15 17_________30
D when choice3,
A _______| |_| |_____________
A signal is an object with a history of values (related to event times, i.e. times at which the E when others;
____________________
signal value changes). B ___________| |_________ (Inertial Delay)
_______ __________ For each of the above, waveforms (time-value pairs) can also be specified.
Signals are declared via signal declaration statements or entity port definitions, and may C ___________| |_| |_________ (Transport Delay)
be of any data type. The declaration syntax is: 10 20 22 35
Examples

Examples Where there are multiple drivers for one signal, a resolution function must be provided to
determine the value to be assigned to the signal from the values supplied by the multiple
signal clock : bit; drivers. This allows simulation of buses with multiple sources/drivers.
signal GND : bit := '0';
signal databus : std_ulogic_vector(15 downto 0); NOTE: The std_logic and std_logic_vector types from the ieee library have
signal addrbus : std_logic_vector(0 to 31);
predefined resolution functions:

Each signal has one or more drivers which determine the value and timing of changes to
Example
the signal. Each driver is a queue of events which indicate when and to what value a signal
is to be changed. Each signal assignment results in the corresponding event queue being signal data_line: std_logic;
modified to schedule the new event. begin
block1:
signal line x data_line <= '1'; -- one driver
...
block2:
10ns 0 Driver of
data_line <= 'Z'; -- 2nd driver
 A <= B after 10ns when condition1 else
statement in the process. Syntax
C after 12ns when condition2 else
D after 11ns; assert (clear /= '1') or (preset /= '1')
Concurrent Procedure Call
report "Both preset and clear are set!"
-- 4-input multiplexer (Choice is a 2-bit vector) severity warning;
An externally defined procedure/subroutine can be invoked, with parameters passed to it
with Choice select Out <=
In0 after 2ns when "00", as necessary. This serves the same function and behaves in the same manner as a
In1 after 2ns when "01", process statement, with any signals in the passed parameters forming a sensitivity list. Generate statement
In2 after 2ns when "10",
In3 after 2ns when "11";
Example A generate statement is an iterative or conditional elaboration of a portion of a description.
-- 2-to-4 decoder (Y = 4-bit and A = 2-bit vectors) This provides a compact way to represent what would ordinarily be a group of statements.
Y <= "0001" after 2ns when A = "00" else ReadMemory (DataIn, DataOut, RW, Clk); -- (where the ReadMemory procedure is defined elsewhere
"0010" after 2ns when A = "01" else Example
"0100" after 2ns when A = "10" else
"1000" after 2ns;
Component instantiation Generate a 4-bit full adder from 1-bit full_adder stages:

-- Tri-state driver: (Y is logic4; X is bit_vector)

Instantiates (i.e. create instances of) predefined components within a design architecture. -- Note that a label is required here
Y <= '0' after 1ns when En = '1' and X = '0' else
'1' after 1ns when En = '1' and X = '1' else Each such component is first declared in the declaration section of that architecture, and add_label: for i in 4 downto 1 generate
'Z' after 1ns; then instantiated one or more times in the body of the architecture. FA: full_adder port map(C(i-1), A(i), B(i), C(i), Sum(i));
end generate;
-- A is a 16-bit vector
In the declaration section: list the component declaration and one or more
A <= (others => '0'); -- set all bits of A to '0'
configuration specifications. The resulting code would look like:
The configuration specification identifies specific architecture(s) to be used for each
The keyword others in the last example indicates that all elements of A not explicitly
FA4: full_adder port map(C(3), A(4), B(4), C(4), Sum(4));
instance of the component. (There may be multiple architectures for a given
listed are to be set to 0 . FA3: full_adder port map(C(2), A(3), B(3), C(3), Sum(3));
component.) FA2: full_adder port map(C(1), A(2), B(2), C(2), Sum(2));
FA1: full_adder port map(C(0), A(1), B(1), C(1), Sum(1));
Process Statement Each instance of a declared component is listed, an instance name assigned, and actual
signals connected to its ports as follows:
An independent sequential process represents the behavior of some portion of a design.
The body of a process is a list of sequential statements.
SEQUENTIAL STATEMENTS
<instance name>: <component name> port map (port list);

Syntax Sequential statements are used to define algorithms to express the behavior of a design
The port list may be in either of two formats: entity. These statements appear in process statements and in subprograms (procedures
label: process (sensitivity list) and functions).
(1) Positional association: signals are connected to ports in the order listed in the
<local declarations>
begin component declaration.
<sequential statements> Example: A1: adder port map (v,w,x,y,z) (v,w, and y must be of type
Wait statement
end process label;
bit_vector , y and z of type bit ) Suspends process/subprogram execution until a signal changes, a condition becomes
(2) Named association: each signal-to-port connection is listed explicitly as true, or a defined time period has elapsed. Combinations of these can also be used.
Example signal => port .
Syntax
DFF: process (clock) Example
begin
if clock = '1' then wait [on <signal> {, <signal>}]
Q <= D after 5ns; A1: adder port map(a => v, b => w, s => y, cin => x, cout => z); [until condition]
QN <= not D after 5ns; [for time expression]
end if;
(The signal ordering is not important in this format)
end process DFF;
Example
The sequential statements in the process are executed in order, commencing with the Concurrent assertion Suspend execution until one of the two conditions becomes true, or for 25ns , whichever
beginning of simulation. After the last statement of a process has been executed, the occurs first.
A concurrent assertion statement checks a condition (occurrence of an event) and issues
process is repeated from the first statement, and continues to repeat until suspended. If
a report if the condition is not true. This can be used to check for timing violations, illegal
the optional sensitivity list is given, a wait on ... statement is inserted after the last wait until clock = '1' or enable /= '1' for 25ns;
conditions, etc. An optional severity level can be reported to indicate the nature of the
sequential statement, causing the process to be suspended at that point until there is an
detected condition.
event on one of the signals in the list, at which time processing resumes with the first
Signal assignment statement
Assign a waveform to one signal driver (edit the event queue). <label>: while <condition> loop -- Convert bit_vector to IEEE std_logic_vector format
<sequence of statements> -- (attributes LENGTH and RANGE are described below)
Example end loop <label>; function bv2slv (b : bit_vector) return std_logic_vector is
variable result : std_logic_vector(b'LENGTH-1 downto 0);
<label>: for <loop variable> in range loop begin
A <= B after 10ns;
<sequence of statements> for i in result'RANGE loop
C <= A after 10ns; -- value of C is current A value
end loop <label>; case b(i) is
when '0' => result(i) := '0';
when '1' => result(i) := '1';
Variable assignment statement NOTE: the label is optional. end case;
end loop;
Update a process/procedure/function variable with an expression. The update takes affect Loop termination statements: allow termination of one iteration, loop, or procedure. return result;
immediately. next [when condition]; : end current loop iteration end;

exit [when condition]; : exit innermost loop entirely

-- Convert bit_vector to unsigned (natural) value
Example return expression; : exit from subprogram function b2n (B : bit_vector) return Natural is
variable S : bit_vector(B'Length - 1 downto 0) := B;
A := B and C; NOTES: variable N : Natural := 0;
D := A; -- value of D is new A value begin
1. The next/exit condition clause is optional. for i in S'Right to S'Left loop
if S(i) = '1' then
2. The return expression is used for functions.
Procedure call N := N + (2**i);
end if;
8. Sequential assertion - same format as a concurrent assertion. end loop;
Invoke an externally-defined subprogram in the same manner as a concurrent procedure
return N;
call. end;
PROCEDURES
Conditional Statements A procedure is a subprogram that is passed parameters and may return values via a Function Calls
parameter list.
Standard if...then and case constructs can be used for selective operations.
signal databus : vector4(15 downto 0);
Example signal internal : bit_vector(15 downto 0);
if <condition> then variable x : integer;
<sequence of statements> ...
procedure <name> (
elsif <condition> then databus <= bv2slv(internal);
signal clk : in vlbit;
<sequence of statements> x := b2n(internal);
constant d : in vlbit;
else
signal data : out vlbit) is
<sequence of statements>
<local variable declarations> Data conversion between ieee types and bit / bit_vector (functions in
end if;
begin ieee.std_logic_1164 )
<sequence of statements>
NOTE: elsif and else clauses are optional. end <proc name>;

case <expression> is Procedure call: <name>(clk1, d1, dout);

when <choice> => <sequence of statements>
when <choice> => <sequence of statements>
... FUNCTIONS
when others => <sequence of statements>
end case; A function is a subprogram that is passed parameters and returns a single value. Unlike
procedures, functions are primarily used in expressions.
NOTE: case choices can be expressions or ranges.
Example
Loop statements
Sequences of statements can be repeated some number of times under the control of
while or for constructs.
 function from to Signal Condition Attributes (for a signal S) Enumeration Data Types (Variable/signal x of data type
S'DELAYED(T) : value of S delayed by T time units
T)
To_bit(sul) std_ulogic bit
S'STABLE(T) : true if no event on S over last T time units T'POS(x) : position number of value of x of type T
std_ulogic_vector ,
To_bitvector(sulv) bit_vector S'QUIET(T) : true if S quiet for T time units T'VAL(x) : value of type T whose position number is x
std_logic_vector
S'LAST_VALUE : value of S prior to latest change T'SUCC(x) : value of type T whose position is x+1
To_StdULogic(b) bit std_ulogic S'LAST_EVENT : time at which S last changed T'PRED(x) : value of type T whose position is x-1
S'LAST_ACTIVE : time at which S last active T'LEFTOF(x) : value of type T whose position is left of x
bit_vector or
To_StdLogicVector(bv) std_logic_vector S'EVENT : true if an event has occurred on S in current cycle T'RIGHTOF(x) : value of type T whose position is right of x
std_ulogic_vector
S'ACTIVE : true if signal S is active in the current cycle

bit_vector or S'TRANSACTION : bit value which toggles each time signal S changes Array Indexes for an Array A (Nth index of array A)
To_StdULogicVector(bv) std_ulogic_vector
std_logic_vector
Examples A'LEFT(N) : left bound of index
bit , std_ulogic , or A'RIGHT(N) : right bound of index
To_X01(v) X01
std_logic if (clock'STABLE(0ns)) then -- change in clock? A'HIGH(N) : upper bound of index
... -- action if no clock edge
A'LOW(N) : lower bound of index
bit , std_ulogic , or else
To_X01Z(v) X01Z ... -- action on edge of clock A'LENGTH(N) : number of values in range of index
std_logic
end if; A'RANGE(N) : range: A'LEFT to A'RIGHT
bit , std_ulogic , or A'REVERSE_RANGE(N) : range A'LEFT downto A'RIGHT
To_UX01(v) UX01 if clock'EVENT and clock = '1' then
std_logic Q <= D after 5ns; -- set Q to D on rising edge of clock
end if; NOTE: For multi-dimensional array, Nth index must be indicated in the attribute
specifier. N may be omitted for a one-dimensional array.
Other ieee.std_logic_1164 functions
Data Type Bounds (Attributes of data type T) Examples
rising_edge(s) - true if rising edge on signal s ( std_ulogic )
falling_edge(s) - true if falling edge on signal s ( std_ulogic ) T'BASE : base type of T
for i in (<data bus>'RANGE) loop
T'LEFT : left bound of data type T ...
T'RIGHT : right bound for i in (d'LEFT(1) to d'RIGHT(1)) loop
OBJECT ATTRIBUTES T'HIGH : upper bound (may differ from left bound) ...

T'LOW : lower bound

An object attribute returns information about a signal or data type.