Bird
Raised Fist0
Verilogprogramming~5 mins

Gate-level delay annotation in Verilog

Choose your learning style10 modes available
Introduction

Gate-level delay annotation helps show how long signals take to travel through logic gates. This makes your design timing more realistic.

When you want to simulate how fast your circuit works in real life.
When checking if signals arrive on time for correct operation.
When testing how delays affect your digital design.
When verifying timing before making a physical chip.
When learning how delays impact circuit behavior.
Syntax
Verilog
and #(delay) and1 (output, input1, input2);
not #(delay) not1 (output, input);
Use #(delay) right after the gate type to specify delay in time units.
Delay is usually given in nanoseconds or the time unit set in your simulation.
Examples
This means the AND gate output changes 5 time units after inputs change.
Verilog
and #(5) and1 (out, a, b);
The NOT gate output changes 2 time units after input changes.
Verilog
not #(2) not1 (out, in);
The OR gate output changes 3 time units after inputs change.
Verilog
or #(3) or1 (out, a, b);
Sample Program

This program shows an AND gate with 4 time units delay and a NOT gate with 2 time units delay. Inputs change over time and output changes follow after the delays.

Verilog
module delay_example();
  reg a, b;
  wire out_and, out_not;

  and #(4) gate_and(out_and, a, b);
  not #(2) gate_not(out_not, a);

  initial begin
    a = 0; b = 0;
    #1 a = 1;
    #1 b = 1;
    #10 $finish;
  end

  initial begin
    $monitor($time, ": a=%b b=%b out_and=%b out_not=%b", a, b, out_and, out_not);
  end
endmodule
OutputSuccess
Important Notes

Delays help simulate real hardware timing but slow down simulation.

Delays are ignored in synthesis (building real chips), only for simulation.

Summary

Gate-level delay annotation adds timing delays to logic gates in simulation.

Use #(delay) after gate type to specify delay in time units.

This helps check if your design works correctly with real-world timing.

Practice

(1/5)
1. What is the purpose of gate-level delay annotation in Verilog?
easy
A. To define the input and output ports of a module
B. To declare variables in a module
C. To specify the time delay for signal propagation through a gate
D. To initialize registers with default values

Solution

  1. Step 1: Understand gate-level delay annotation

    Gate-level delay annotation is used to add timing delays to logic gates in simulation.
  2. Step 2: Identify its purpose

    This delay models the real-world time it takes for signals to propagate through gates, helping verify timing correctness.
  3. Final Answer:

    To specify the time delay for signal propagation through a gate -> Option C
  4. Quick Check:

    Gate delay = specify propagation time [OK]
Hint: Gate delays model real signal timing in simulation [OK]
Common Mistakes:
  • Confusing delay annotation with variable declaration
  • Thinking delay sets input/output ports
  • Assuming delay initializes registers
2. Which of the following is the correct syntax to add a 5-time-unit delay to an AND gate in Verilog?
easy
A. and #(5) (out, in1, in2);
B. and #5 (out, in1, in2);
C. and delay(5) (out, in1, in2);
D. and (out, in1, in2) #5;

Solution

  1. Step 1: Recall Verilog gate delay syntax

    The delay is specified immediately after the gate type using #delay without parentheses.
  2. Step 2: Match correct syntax

    and #5 (out, in1, in2); uses 'and #5 (out, in1, in2);' which is the correct form.
  3. Final Answer:

    and #5 (out, in1, in2); -> Option B
  4. Quick Check:

    Delay after gate type with #number [OK]
Hint: Use #number immediately after gate type for delay [OK]
Common Mistakes:
  • Using parentheses around delay value
  • Placing delay after port list
  • Writing delay as a function call
3. Given the following Verilog code snippet, what is the delay before out changes after in1 or in2 changes?
and #3 (out, in1, in2);
medium
A. 0 time units
B. 5 time units
C. 1 time unit
D. 3 time units

Solution

  1. Step 1: Identify the delay annotation

    The code uses '#3' after the 'and' gate, indicating a 3-time-unit delay.
  2. Step 2: Understand delay effect

    This means output changes occur 3 time units after input changes.
  3. Final Answer:

    3 time units -> Option D
  4. Quick Check:

    Delay #3 means 3 time units [OK]
Hint: Delay number equals output wait time after input change [OK]
Common Mistakes:
  • Assuming delay is zero if not explicitly stated
  • Confusing delay with input change time
  • Choosing wrong delay value
4. Identify the error in the following Verilog gate-level delay annotation:
or (out, in1, in2) #4;
medium
A. Delay must be specified immediately after gate type, not after port list
B. Delay value cannot be 4
C. The gate type 'or' is invalid
D. Port list must be enclosed in square brackets

Solution

  1. Step 1: Check delay placement

    Delay must come immediately after the gate type, not after the port list.
  2. Step 2: Analyze given code

    The code places '#4' after the port list, which is incorrect syntax.
  3. Final Answer:

    Delay must be specified immediately after gate type, not after port list -> Option A
  4. Quick Check:

    Delay after gate type, not ports [OK]
Hint: Place #delay right after gate type, before ports [OK]
Common Mistakes:
  • Putting delay after port list
  • Using invalid gate names
  • Wrong port list syntax
5. You want to model an AND gate with different rise and fall delays: 2 time units for rising output and 4 time units for falling output. Which is the correct Verilog gate-level delay annotation?
hard
A. and #(2,4) (out, in1, in2);
B. and #(4,2) (out, in1, in2);
C. and #(2) #(4) (out, in1, in2);
D. and #2 #4 (out, in1, in2);

Solution

  1. Step 1: Understand Verilog rise/fall delay syntax

    Verilog allows specifying rise and fall delays as #(rise, fall) after the gate type.
  2. Step 2: Match delays to correct order

    The first number is rise delay, second is fall delay, so #(2,4) means 2 units rise, 4 units fall.
  3. Final Answer:

    and #(2,4) (out, in1, in2); -> Option A
  4. Quick Check:

    Use #(rise, fall) for different delays [OK]
Hint: Use #(rise, fall) to set different delays [OK]
Common Mistakes:
  • Reversing rise and fall values
  • Using multiple # delays separately
  • Incorrect syntax with multiple #
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard