Testbench module structure in Verilog - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to declare a testbench module named 'tb'.

Verilog

module [1]();
endmodule

Drag options to blanks, or click blank then click option'

Amain

Btestbench

Ctb

Dtop

Attempts:

3 left

💡 Hint

Common Mistakes

Using reserved keywords as module names.

Forgetting to add parentheses after the module name.

The testbench module is usually named 'tb' for simplicity.

2fill in blank

medium

Complete the code to instantiate a device under test (DUT) named 'dut_inst' inside the testbench.

Verilog

module tb();
  [1] dut_inst();
endmodule

Drag options to blanks, or click blank then click option'

Amodule

Bdut

Cdevice

Dtestbench

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'module' keyword instead of module name.

Confusing instance name with module name.

The DUT is instantiated by its module name, often 'dut'.

3fill in blank

hard

Fix the error in the initial block to start the simulation with a delay of 10 time units.

Verilog

module tb();
  initial begin
    #[1];
    $finish;
  end
endmodule

Drag options to blanks, or click blank then click option'

A10

B5

C1

D0

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero delay which ends simulation immediately.

Using delay without '#' symbol.

The delay '#10;' waits for 10 time units before executing the next statement.

4fill in blank

hard

Fill both blanks to declare a clock signal 'clk' and toggle it every 5 time units.

Verilog

module tb();
  reg [1] = 0;
  always #[2] [1] = ~[1];
endmodule

Drag options to blanks, or click blank then click option'

Aclk

Brst

C5

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong signal name like 'rst' for clock.

Incorrect delay value for toggling clock.

The clock signal 'clk' is declared as a reg and toggled every 5 time units.

5fill in blank

hard

Fill all three blanks to declare a reset signal 'rst', initialize it to 1, and de-assert it after 15 time units.

Verilog

module tb();
  reg [1] = 1;
  initial begin
    #[2] [1] = [3];
  end
endmodule

Drag options to blanks, or click blank then click option'

Aclk

Brst

C0

D15

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong signal name for reset.

Setting reset to 1 instead of 0 after delay.

The reset signal 'rst' is initialized to 1 and set to 0 after 15 time units to release reset.

Practice

1. What is the main purpose of a testbench module in Verilog?

easy

A. To simulate and verify the behavior of a design module

B. To synthesize the hardware design for FPGA

C. To define input/output ports for the design

D. To optimize the design for speed

Solution

1. Step 1: Understand the role of a testbench

   A testbench is used to simulate and verify how a design behaves before hardware implementation.

2. Step 2: Differentiate from synthesis and design definition

   It does not synthesize hardware or define ports; it only tests the design by applying inputs and checking outputs.

3. Final Answer:

   To simulate and verify the behavior of a design module -> Option A

4. Quick Check:

   Testbench = simulation and verification [OK]

Hint: Testbench runs simulations, not synthesis or hardware creation [OK]

Common Mistakes:

• Confusing testbench with synthesis module
• Thinking testbench defines ports for hardware
• Assuming testbench optimizes design

2. Which of the following is the correct way to declare a testbench module in Verilog?

easy

A. module testbench(input clk, output result); endmodule

B. module testbench(input clk); endmodule

C. module testbench(); endmodule

D. module testbench(output result); endmodule

Solution

1. Step 1: Recall testbench port requirements

   A testbench usually has no ports because it internally generates signals and drives the design under test.

2. Step 2: Check each option for ports

   Only module testbench(); endmodule declares a module with no ports, which is typical for testbenches.

3. Final Answer:

   module testbench(); endmodule -> Option C

4. Quick Check:

   Testbench has no ports = module testbench(); endmodule [OK]

Hint: Testbenches usually have empty port lists () [OK]

Common Mistakes:

• Adding input/output ports to testbench module
• Confusing testbench with design module ports
• Forgetting to close module declaration

3. Given the following testbench snippet, what will be printed during simulation?

module testbench();
  reg clk = 0;
  initial begin
    $monitor("Time=%0t clk=%b", $time, clk);
    #5 clk = 1;
    #5 clk = 0;
    #5 $finish;
  end
endmodule

medium

A. Time=0 clk=0 only

B. Time=0 clk=1\nTime=5 clk=0\nTime=10 clk=1

C. No output because $monitor is missing parentheses

D. Time=0 clk=0\nTime=5 clk=1\nTime=10 clk=0

Solution

1. Step 1: Understand $monitor behavior

   $monitor prints the message whenever any listed variable changes, starting at time 0.

2. Step 2: Trace clk changes and times

   Initially clk=0 at time 0, then clk=1 at time 5, clk=0 at time 10, then simulation ends at 15.

3. Final Answer:

   Time=0 clk=0\nTime=5 clk=1\nTime=10 clk=0 -> Option D

4. Quick Check:

   $monitor prints on changes = Time=0 clk=0\nTime=5 clk=1\nTime=10 clk=0 [OK]

Hint: Trace signal changes and $monitor prints at each change [OK]

Common Mistakes:

• Confusing $monitor with $display (only prints once)
• Ignoring initial value print at time 0
• Misreading timing delays (#5)

4. Identify the error in this testbench code snippet:

module testbench();
  reg clk;
  initial begin
    clk = 0;
    forever #5 clk = ~clk;
  end
endmodule

medium

A. Using forever inside initial block is not allowed

B. No error; code is correct

C. Missing semicolon after forever statement

D. clk should be declared as wire, not reg

Solution

1. Step 1: Check syntax of forever inside initial

   Using forever inside an initial block to toggle clk is valid and common for clock generation.

2. Step 2: Verify reg declaration and semicolons

   clk is correctly declared as reg, and semicolons are properly placed.

3. Final Answer:

   No error; code is correct -> Option B

4. Quick Check:

   forever in initial with reg clk = correct [OK]

Hint: forever loops inside initial are valid for clocks [OK]

Common Mistakes:

• Thinking forever is illegal inside initial
• Confusing reg and wire for clock signals
• Missing semicolons elsewhere (not here)

5. You want to create a testbench that applies a reset signal for 10 time units, then releases it, and monitors a 4-bit output signal out. Which code snippet correctly implements this behavior?

hard

A. module tb();
reg reset = 1;
wire [3:0] out;
design dut(.reset(reset), .out(out));
initial begin
#10 reset = 0;
$monitor("out=%b", out);
end
endmodule

B. module tb();
reg reset;
wire [3:0] out;
design dut(.reset(reset), .out(out));
initial begin
reset = 0;
#10 reset = 1;
$monitor("out=%b", out);
end
endmodule

C. module tb();
reg reset = 0;
wire [3:0] out;
design dut(.reset(reset), .out(out));
initial begin
#10 reset = 1;
$monitor("out=%b", out);
end
endmodule

D. module tb();
reg reset = 1;
wire [3:0] out;
design dut(.reset(reset), .out(out));
initial begin
#5 reset = 0;
$monitor("out=%b", out);
end
endmodule

Solution

1. Step 1: Check initial reset value and timing

   Reset should start at 1 (active), then after 10 time units go to 0 (inactive). Only module tb(); reg reset = 1; wire [3:0] out; design dut(.reset(reset), .out(out)); initial begin #10 reset = 0; $monitor("out=%b", out); end endmodule does this correctly.

2. Step 2: Confirm $monitor usage and signal connections

   $monitor is called after reset release to watch output changes; design instance connects reset and out signals properly.

3. Final Answer:

   module tb(); reg reset = 1; wire [3:0] out; design dut(.reset(reset), .out(out)); initial begin #10 reset = 0; $monitor("out=%b", out); end endmodule -> Option A

4. Quick Check:

   Reset active 10 units then release + monitor = module tb(); reg reset = 1; wire [3:0] out; design dut(.reset(reset), .out(out)); initial begin #10 reset = 0; $monitor("out=%b", out); end endmodule [OK]

Hint: Start reset=1, delay 10, then reset=0, monitor output [OK]

Common Mistakes:

• Setting reset low initially instead of high
• Delaying reset assertion instead of deassertion
• Placing $monitor before reset release