PROVIDER - the strongly typed HDL of safety-critical engineering
VHDL
VHDL came out of the 1980s VHSIC programme and is maintained as IEEE 1076 through the 2019 revision, with strong typing that stops width errors at compile time; it dominates European safety-critical and long-lived projects, at the price of verbosity and thin open-source synthesis.
3.9pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
VHDL (VHSIC Hardware Description Language) came out of the US Department of Defense VHSIC programme in the 1980s and became IEEE 1076 in 1987, with revisions in 1993, 2000, 2002, 2008 and 2019. Its design goal is maintainability at scale: strong typing, explicit widths, packages and configurations break a design into reusable units.
In the languages and frameworks category it stands beside Verilog as a mainstream HDL, but with a higher share in European aerospace, rail and industrial control, where safety-critical projects often require VHDL plus formal verification tooling.
Key Strengths
- Strong typing protection: width and type mismatches fail at compile time, avoiding the silent truncation common in Verilog
- Hierarchical structure: separate entity and architecture, reusable packages and configuration binding suit designs built by dozens of engineers
- Long-lived standard: IEEE 1076-2019 keeps a compatible path back to 1993, so old IP still compiles
- Full vendor support: Vivado, Quartus, Libero, Questa and Riviera all provide complete flows
- Maturing verification stack: OSVVM and UVVM add coverage-driven and bus verification frameworks
Product Ecosystem
Standard revisions
IEEE 1076-1987/1993/2000/2002/2008/2019; 2008 added generic packages and external names, and 2019 added interfaces and conditional analysis.
Tools
GHDL is the open-source simulator; commercial options include Questa, Riviera-PRO and Vivado Simulator, while synthesis relies on vendor tools or Synplify.
Verification frameworks
OSVVM provides randomisation and functional coverage, and UVVM targets bus and structured verification.
Limitations
- Verbose syntax: entity, architecture, signal and variable declarations push code volume to roughly 1.5 to 2 times the Verilog equivalent
- Weak open-source synthesis: production still depends on vendor tools
- Smaller community: fewer tutorials, open cores and answers than in the Verilog world
- Verification is external: constrained random and coverage come from OSVVM or UVVM rather than the language
Use Cases
- Aerospace and rail signalling (★★★★★): maintainability and certification demands are high
- Industrial control and power electronics (★★★★): long-lived, multi-team projects
- FPGA teaching and research (★★★★): the type system teaches hardware semantics
- Quick prototypes and small projects (★★★): Verilog needs less code
Pricing
| Item | Price | Notes |
|---|---|---|
| GHDL | $0 | Open-source simulator under GPL |
| Free vendor editions | $0 | Vivado and Quartus free editions cover mid-size devices |
| Commercial simulation and synthesis | Per seat or contract | Questa, Riviera and Synplify require licences |
Learning and small projects can run entirely on free tools; production and certification work usually needs commercial licences and support.
FAQ
- Can VHDL and Verilog be mixed? Yes, mainstream simulators support mixed-language simulation, but mixing in synthesis adds tool dependencies, so split cleanly at module boundaries.
- What separates
signalfromvariable? Signals update with a delta delay and model wires and registers; variables assign immediately and belong inside processes, and misuse makes simulation and synthesis disagree. - Is VHDL still worth learning? Demand is stable in Europe and safety-critical industries, and the typing discipline helps when writing Verilog too. Compare routes under languages and frameworks.
Code Examples
Counter with synchronous reset
library ieee;
use ieee.std_logic_1164.all;
use ieee.numeric_std.all;
entity counter is
generic (WIDTH : positive := 8);
port (
clk : in std_logic;
rst : in std_logic;
en : in std_logic;
q : out std_logic_vector(WIDTH-1 downto 0)
);
end entity;
architecture rtl of counter is
signal cnt : unsigned(WIDTH-1 downto 0) := (others => '0');
begin
process (clk)
begin
if rising_edge(clk) then
if rst = '1' then
cnt <= (others => '0');
elsif en = '1' then
cnt <= cnt + 1;
end if;
end if;
end process;
q <= std_logic_vector(cnt);
end architecture;
Arithmetic runs on unsigned and converts back before output, which is standard VHDL practice.
Testbench clock generation
library ieee;
use ieee.std_logic_1164.all;
entity tb_counter is end entity;
architecture sim of tb_counter is
signal clk, rst, en : std_logic := '0';
signal q : std_logic_vector(7 downto 0);
begin
uut: entity work.counter
port map (clk => clk, rst => rst, en => en, q => q);
clk <= not clk after 5 ns; -- 100MHz
process
begin
rst <= '1'; wait for 12 ns; rst <= '0';
en <= '1'; wait for 200 ns;
wait;
end process;
end architecture;
after 5 ns sets the half period and wait for sequences the stimulus.
Community & Resources
- VHDLwhiz: VHDL tutorials, examples and engineering practice
- HDL Works: HDL design entry and verification tools
- GitHub VHDL topic: open IP cores and testbenches
- GitHub Verilog topic: the other mainstream HDL for comparison
- Accellera Systems Initiative: related HDL standards activity