PROVIDER - the de facto language of chip design and verification
SystemVerilog
SystemVerilog was proposed by Accellera in 2002 and became IEEE 1800 in 2005, adding classes, interfaces, SVA assertions and coverage on top of Verilog; it is now the default for chip verification, with language size and tool licensing as the main costs.
4.3pts
Detailed Notes
Pros 5 items
Cons 4 items
Service Overview
SystemVerilog was proposed by Accellera in 2002 and became IEEE 1800 in 2005, with revisions in 2012, 2017 and 2023. It is a superset of Verilog-2005: the original RTL syntax remains, while classes, randomisation, assertions, coverage and interfaces are added for verification.
In the languages and frameworks category it represents the unification of design and verification: most new SoC RTL and testbenches are written in it, and Verilog has become a subset.
Key Strengths
- Verification built in: SVA assertions, constrained random and functional coverage are language features, not external scripts
- Interfaces and packages:
interfacebundles bus signals andpackageshares types and functions, cutting duplicate declarations - Verilog compatible: existing Verilog compiles directly, so migration is incremental
- Mature UVM ecosystem: Accellera UVM supplies reusable verification components and register models
- Single toolchain: mainstream simulators and synthesis tools accept it as the primary format
Product Ecosystem
Standards
IEEE 1800-2005/2012/2017/2023; Accellera drives the standard and maintains UVM.
Simulation and synthesis
VCS, Questa and Xcelium lead commercially; Verilator covers most of the synthesizable subset and part of the verification features.
Methodologies
UVM provides agents, sequences and scoreboards, and formal tools consume SVA assertions directly.
Limitations
- Language breadth: synthesizable design syntax and non-synthesizable verification syntax share one grammar, so the boundary needs experience
- Synthesis limits: classes, dynamic arrays and most assertions fail at synthesis
- UVM cost: testbench code can exceed the RTL several times over, which is hard for small teams
- Expensive licences: commercial simulators are priced per seat or project, and open-source alternatives fall short on verification features
Use Cases
- SoC and IP verification (★★★★★): constrained random with coverage is the industry default
- Complex FPGA interfaces (★★★★): interfaces and packages remove boilerplate
- Formal and assertion-driven design (★★★★): SVA feeds formal tools directly
- Small teaching labs (★★★): Verilog is lighter and sufficient
Pricing
| Item | Price | Notes |
|---|---|---|
| Standard and UVM | $0 | IEEE standard and Accellera UVM are publicly available |
| Verilator | $0 | Open-source simulation and modelling |
| Commercial simulators | Per seat or contract | VCS, Questa and Xcelium licences are substantial |
The language and libraries are free; cost concentrates in commercial simulators and verification headcount.
FAQ
- Is SystemVerilog synthesizable? Only the synthesizable subset is; classes, dynamic memory and assertions serve verification. Restrict RTL to
always_ff,always_combandlogicstyle constructs. - Must you use UVM? For large projects yes; small blocks are better served by a light testbench plus SVA before adopting the framework.
- What learning order works? Master Verilog sequential and combinational modelling first, then SystemVerilog types, interfaces and assertions. Compare with Verilog under languages and frameworks.
Code Examples
always_ff with an assertion
module counter #(parameter int WIDTH = 8) (
input logic clk,
input logic rst_n,
input logic en,
output logic [WIDTH-1:0] q
);
always_ff @(posedge clk or negedge rst_n) begin
if (!rst_n) q <= '0;
else if (en) q <= q + 1'b1;
end
property p_no_overflow;
@(posedge clk) disable iff (!rst_n) (q != '1) |-> (q <= q + 1);
endproperty
a_no_overflow: assert property (p_no_overflow);
endmodule
always_ff states the intent explicitly, and property plus assert keep checks beside the design.
Interface and testbench fragment
interface bus_if (input logic clk);
logic valid;
logic ready;
logic [31:0] data;
modport drv (output valid, data, input ready);
modport mon (input valid, ready, data);
endinterface
module tb;
logic clk = 0;
always #5 clk = ~clk;
bus_if bus (clk);
initial begin
bus.valid = 1;
bus.data = 32'hDEAD_BEEF;
#20 bus.valid = 0;
end
endmodule
modport splits one signal set by direction for driver and monitor roles.
Community & Resources
- Accellera Systems Initiative: standards body for SystemVerilog and UVM
- GitHub SystemVerilog topic: open verification platforms and IP
- GitHub Verilog topic: entry material for the synthesizable subset
- GitHub VHDL topic: the other mainstream HDL
- GitHub STM32 topic: the microcontroller path towards programmable logic