Register (multi-bit flip-flop) in Verilog - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a register in digital design?

A register is a group of flip-flops used to store multiple bits of data simultaneously. It holds binary information and can be used to save state or data temporarily.

beginner

How does a multi-bit flip-flop register differ from a single flip-flop?

A multi-bit flip-flop register stores multiple bits at once, usually as a vector, while a single flip-flop stores only one bit. Registers allow parallel storage of data.

beginner

Explain the role of the clock signal in a register.

The clock signal controls when the register updates its stored data. On a clock edge (usually rising), the register captures the input data and holds it until the next clock event.

intermediate

What is the purpose of a reset signal in a multi-bit register?

A reset signal sets the register to a known state (usually all zeros) asynchronously or synchronously, clearing stored data to avoid unpredictable behavior.

intermediate

Write a simple Verilog code snippet for an 8-bit register with synchronous reset.

module register_8bit(input clk, input reset, input [7:0] d, output reg [7:0] q); always @(posedge clk) begin if (reset) q <= 8'b0; else q <= d; end endmodule

What does a multi-bit register store?

A Only one bit of data

B Multiple bits of data simultaneously

C Only clock signals

D Only reset signals

A multi-bit register stores multiple bits of data at the same time using multiple flip-flops.

When does a register update its stored value?

A On the clock edge

B Continuously without clock

C Only when reset is active

D When power is off

Registers update their stored data on a clock edge, usually the rising edge.

What is the effect of a synchronous reset in a register?

A Clears the register on the clock edge when reset is active

B Clears the register immediately without clock

C Prevents the register from storing data

D Inverts the stored data

A synchronous reset clears the register only on the clock edge when the reset signal is active.

In Verilog, which keyword is used to declare a register that holds data?

A output

B wire

C reg

D input

The 'reg' keyword declares a variable that can hold data in Verilog.

What happens if you do not use a clock in a register design?

A The register resets automatically

B The register stores data faster

C The register outputs random data

D The register cannot store data reliably

Without a clock, the register cannot synchronize data storage, so it won't work reliably.

Describe how a multi-bit register works and why the clock signal is important.

Think about how data is stored and when it changes.

Write a simple Verilog module for a 4-bit register with synchronous reset and explain each part.

Focus on the structure and how reset and clock control data.

Practice

1.

What is the main purpose of a multi-bit register in Verilog?

easy

A. To store multiple bits of data and update them on clock edges

B. To perform arithmetic operations on data

C. To generate clock signals

D. To convert analog signals to digital

Solution

1. Step 1: Understand the function of a register

   A register is used to hold data bits temporarily in digital circuits.

2. Step 2: Recognize clock edge behavior

   Registers update their stored data only on clock edges, making them synchronous storage elements.

3. Final Answer:

   To store multiple bits of data and update them on clock edges -> Option A

4. Quick Check:

   Register = multi-bit storage updated on clock edges [OK]

Hint: Registers store bits and update only on clock edges [OK]

Common Mistakes:

• Confusing registers with combinational logic
• Thinking registers generate clocks
• Assuming registers perform arithmetic

2.

Which of the following is the correct way to declare an 8-bit register in Verilog?

?

easy

A. reg [7:0] my_reg;

B. reg my_reg[7:0];

C. register [8] my_reg;

D. reg my_reg : 8;

Solution

1. Step 1: Recall Verilog register declaration syntax

   Registers are declared with 'reg' keyword followed by bit range in square brackets before the name.

2. Step 2: Check each option

   reg [7:0] my_reg; uses correct syntax: 'reg [7:0] my_reg;'. Others have syntax errors or wrong keywords.

3. Final Answer:

   reg [7:0] my_reg; -> Option A

4. Quick Check:

   Correct reg declaration = reg [7:0] name; [OK]

Hint: Use reg [MSB:LSB] name; to declare multi-bit registers [OK]

Common Mistakes:

• Placing bit range after variable name
• Using 'register' keyword instead of 'reg'
• Using colon instead of square brackets

3.

Given the following Verilog code, what will be the value of reg_out after the positive edge of clk if reset is 0 and data_in is 8'b10101010?

module reg_example(input clk, input reset, input [7:0] data_in, output reg [7:0] reg_out);
  always @(posedge clk or posedge reset) begin
    if (reset)
      reg_out <= 8'b00000000;
    else
      reg_out <= data_in;
  end
endmodule

medium

A. 8'b00000000

B. 8'b10101010

C. 8'b11111111

D. No change in reg_out

Solution

1. Step 1: Analyze the always block sensitivity

   The block triggers on positive edge of clk or reset. If reset is high, reg_out resets to zero.

2. Step 2: Check conditions given

   Reset is 0, so reg_out will be assigned data_in value on clk rising edge, which is 8'b10101010.

3. Final Answer:

   8'b10101010 -> Option B

4. Quick Check:

   Reset=0, reg_out = data_in = 10101010 [OK]

Hint: If reset=0, reg_out updates to data_in on clk edge [OK]

Common Mistakes:

• Assuming reset clears reg_out when reset=0
• Ignoring clock edge sensitivity
• Confusing blocking and non-blocking assignments

4.

Identify the error in this Verilog register code snippet:

always @(posedge clk) begin
  if (reset == 1)
    reg_data = 8'b0;
  else
    reg_data <= input_data;
end

medium

A. Incorrect bit width for reg_data

B. Missing sensitivity to reset signal

C. Using blocking assignment (=) for reset instead of non-blocking (<=)

D. Using '==' instead of '=' in if condition

Solution

1. Step 1: Review assignment types in sequential blocks

   Inside always @(posedge clk), non-blocking assignments (<=) should be used for registers to avoid race conditions.

2. Step 2: Identify the error in reset assignment

   The reset assignment uses blocking '=' which is incorrect; it should be '<=' to match the else branch.

3. Final Answer:

   Using blocking assignment (=) for reset instead of non-blocking (<=) -> Option C

4. Quick Check:

   Use <= for all register assignments in clocked always blocks [OK]

Hint: Use <= for all assignments inside clocked always blocks [OK]

Common Mistakes:

• Mixing blocking and non-blocking assignments
• Not including reset in sensitivity list (not error here but common)
• Using '==' in if condition is correct syntax

5.

You want to create a parameterized multi-bit register module with asynchronous reset that can hold WIDTH bits. Which of the following code snippets correctly implements this?

module param_reg #(parameter WIDTH = 8) (
  input clk,
  input reset,
  input [WIDTH-1:0] data_in,
  output reg [WIDTH-1:0] data_out
);
  always @(posedge clk or posedge reset) begin
    if (reset)
      data_out <= {WIDTH{1'b0}};
    else
      data_out <= data_in;
  end
endmodule

hard

A. Incorrect: data_out declared as wire instead of reg

B. Incorrect: missing parameter declaration

C. Incorrect: synchronous reset used instead of asynchronous

D. Correct parameterized register with asynchronous reset

Solution

1. Step 1: Check parameter usage

   The module declares parameter WIDTH and uses it to size inputs and outputs correctly.

2. Step 2: Verify asynchronous reset and assignments

   The always block triggers on posedge clk or reset, and reset asynchronously clears data_out using replication operator.

3. Step 3: Confirm data_out declared as reg

   data_out is declared as reg, which is required for assignment inside always block.

4. Final Answer:

   Correct parameterized register with asynchronous reset -> Option D

5. Quick Check:

   Parameter + async reset + reg output = correct [OK]

Hint: Use parameter and replication operator for flexible reset [OK]

Common Mistakes:

• Forgetting parameter declaration
• Using synchronous reset when async needed
• Declaring output as wire instead of reg