You already have everything you need. EcrioniX ships a free online Verilog / SystemVerilog simulator with compile, run, and waveform viewing — so this course never asks you to fight license servers on day one.
ecrionix.org/tools/verilog-simulator/ — write RTL + testbench in the browser, hit Run, inspect waves.
Type modules and testbenches with syntax highlighting — same place you will paste course labs.
Uses a real Icarus Verilog-style flow under the hood. Syntax errors show up immediately.
See clocks, resets, and data change over time — the skill that separates “code that compiles” from “design that works.”
Works in a normal browser. Perfect for students and switchers.
Follow this exact sequence every time you open the lab bench. After a few repetitions it becomes automatic.
endmodule, or port mismatches. Re-run.clk, rst_n, then your signals of interest.Text mock-up of the simulator layout — your actual UI may label buttons slightly differently.
Paste both blocks into the simulator. Run, then open waves. out must track in after reset.
// Lesson 0.2 — simplest DUT: wire passthrough module passthrough ( input wire in, output wire out ); assign out = in; endmodule
`timescale 1ns/1ps
module tb_passthrough;
reg in;
wire out;
passthrough u_dut (.in(in), .out(out));
initial begin
in = 0;
#10 in = 1;
#10 in = 0;
#10 in = 1;
#20 $finish;
end
initial begin
$dumpfile("waves.vcd");
$dumpvars(0, tb_passthrough);
end
endmodule
Goal: prove you can edit → run → read a wave. That loop is 80% of learning RTL.
If it fails: read the compile log first (typos, missing endmodule, wrong port names). Do not stare at waves until compile is clean.
For sequential designs (Modules 4+), outputs often update one clock after the input change. Combo logic (like passthrough) changes in the same timestep.
| Tool | Best for | Weak for |
|---|---|---|
$display / log | Packet bytes, FSM state names, pass/fail banners, long sims with few checkpoints | Timing relationships, glitches, multi-signal alignment |
| Waveforms (VCD) | Clock/reset/debugging timing, buses, I2C SCL/SDA, "what happened at this edge?" | Reading 10 000 lines of hex dumps |
$display is a diary entry ("state became IDLE at 500 ns"). Waveforms are security camera footage — you see who moved when.
Course default: use both. Dump waves always; add $display for high-level milestones in testbenches (especially Module 10–11 I2C).
Even in a browser simulator, treat files like a mini project:
fifo.v, fifo_tb.v.tb_<dut>; instance u_dut.lesson04_reset_bug.png.Common mistake: editing the DUT but running an old cached version. After big changes, hard-refresh the page or re-paste the full file to be sure.
Add `timescale 1ns/1ps at top of TB so delays and waves make sense.
Sim runs but waves are empty. Always include dump calls in TB initial block.
$finish before signals toggle — zoom shows flat lines. Extend delays or delay finish.
Uninitialized regs show as X in waves. Drive reset explicitly in first initial block.
When a lesson says “open the simulator,” it means this tool — not a separate paid suite.
scl/sda together later)