PROVIDER - the veteran HDL for digital design and RTL
Verilog
Verilog was proposed by Phil Moorby in 1984 and models behavioural, RTL and gate level design from one source, standardized as IEEE 1364 through the 2005 revision; it is easy to learn, but loose typing and the absence of a verification methodology pushed large projects to SystemVerilog.
4pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
Verilog was proposed in 1984 by Phil Moorby at Gateway Design Automation and became an industrial standard with the Verilog-XL simulator in 1985. It describes digital circuits as modules and wires, expressing timing and combinational logic in C-like syntax, and is one of the two mainstream HDLs alongside VHDL.
In the languages and frameworks category it is a language that describes hardware rather than executing instructions: the code becomes gates and sequential logic, so small stylistic choices decide resource usage and achievable clock frequency.
Key Strengths
- One source, three uses: behavioural simulation, RTL synthesis and gate-level netlist verification
- Low syntax barrier: C-like expressions and module structure, so software engineers can write simulatable code within 1 week
- Full tool coverage: open-source Icarus Verilog and Verilator alongside commercial VCS, Questa and Xsim
- Rich learning material: textbooks, open IP and online courses exceed other HDLs, making it a good first hardware language
- Compatible upward path: SystemVerilog is its superset, so migrating later is cheap
Product Ecosystem
Language and standards
IEEE 1364-1995, 1364-2001 and 1364-2005; SystemVerilog (IEEE 1800) extends the family.
Simulation and synthesis
Icarus Verilog simulates, Verilator compiles RTL into C++ models, and synthesis runs in Vivado, Quartus or Design Compiler.
Common idioms
always @(posedge clk) describes sequential logic, assign describes combinational logic, and a testbench uses initial with #delay for stimulus.
Limitations
- Loose typing: width mismatches truncate silently, so simulation can pass while synthesized behaviour differs
- No verification methodology: constrained random, functional coverage and assertions require SystemVerilog and UVM
- Synthesizable subset limits:
initial, delays and several system tasks work only in simulation - Migration pressure: new SoC projects use SystemVerilog, reducing pure Verilog positions
Use Cases
- FPGA learning and course labs (★★★★★): simple syntax and cheap tools
- Small to mid-size RTL design (★★★★): state machines and interface logic
- IP simulation (★★★★): much open IP is written in Verilog
- Large SoCs and verification platforms (★★): go straight to SystemVerilog
Pricing
| Item | Price | Notes |
|---|---|---|
| Icarus Verilog and Verilator | $0 | Open-source simulation and modelling |
| Vendor FPGA tools | $0 | Free editions of Vivado and Quartus cover mid-size devices |
| Commercial simulators | Per seat or contract | VCS and Questa are expensive and usually project licensed |
Learning and small designs cost almost nothing; commercial simulators and ASIC tape-out dominate the budget.
FAQ
- Verilog or VHDL? Team background decides: software-trained teams usually pick Verilog, while safety-critical and European teams often prefer VHDL. Tools support mixed-language simulation either way.
- What is the difference between
=and<=? Use blocking=in combinational logic and non-blocking<=in sequential logic; mixing them causes simulation and synthesis to diverge. - Should you still learn SystemVerilog? Yes, at minimum
logic,always_ff,interfaceand assertions. Related routes are listed under languages and frameworks.
Code Examples
Counter module
module counter #(parameter WIDTH = 8) (
input wire clk,
input wire rst_n,
input wire en,
output reg [WIDTH-1:0] q
);
always @(posedge clk or negedge rst_n) begin
if (!rst_n) q <= {WIDTH{1'b0}};
else if (en) q <= q + 1'b1;
end
endmodule
Sequential logic uses non-blocking assignment, and the asynchronous reset appears in the sensitivity list.
Testbench with clock and stimulus
module tb_counter;
reg clk = 0;
reg rst_n = 0;
reg en = 0;
wire [7:0] q;
counter uut (.clk(clk), .rst_n(rst_n), .en(en), .q(q));
always #5 clk = ~clk; // 100MHz
initial begin
#12 rst_n = 1;
#10 en = 1;
#200 en = 0;
#20 $finish;
end
endmodule
#5 counts time units, and a timescale directive pins them to real nanoseconds.
Community & Resources
- Verilog.com: language references and tool pointers
- GitHub Verilog topic: open IP, samples and peripheral controllers
- GitHub SystemVerilog topic: verification methods and superset features
- Accellera Systems Initiative: standards body behind SystemVerilog
- GitHub Arduino topic: the microcontroller path into hardware