Synthesis warnings and how to fix them in Verilog - Mini Project: Build & Apply

Synthesis warnings and how to fix them

📖 Scenario: You are designing a simple digital circuit using Verilog. Sometimes, when you run synthesis tools, you get warnings. These warnings tell you about potential problems in your code that might cause the circuit to not work as expected.In this project, you will learn how to spot common synthesis warnings and fix them step-by-step.

🎯 Goal: Build a small Verilog module that counts from 0 to 3 repeatedly. You will write the code, add a control signal, fix a common synthesis warning about inferred latches, and finally print a message to confirm the fix.

📋 What You'll Learn

Create a Verilog module with a 2-bit counter

Add a reset signal to initialize the counter

Fix the synthesis warning about inferred latches by adding an else branch

Display a message confirming the fix

💡 Why This Matters

🌍 Real World

Digital designers often get synthesis warnings that can cause hardware bugs. Learning to fix these warnings early helps build reliable circuits.

💼 Career

Understanding synthesis warnings and how to fix them is essential for FPGA and ASIC engineers to ensure their designs work correctly in real hardware.

1

Create a simple 2-bit counter module

Write a Verilog module named counter with inputs clk and reset, and a 2-bit output count. Inside, create a register count that increments by 1 on every positive edge of clk. Do not add reset logic yet.

Verilog

module counter(input clk, input reset, output reg [1:0] count);
// Your code here
endmodule

Hint

Use an always @(posedge clk) block and increment count by 1 inside it.

2

Add reset logic to initialize the counter

Modify the always @(posedge clk) block to check if reset is high. If so, set count to 0. Otherwise, increment count by 1.

Verilog

module counter(input clk, input reset, output reg [1:0] count);
    always @(posedge clk) begin
        // Add reset check here
        // Your code here
    end
endmodule

Hint

Use an if-else statement inside the always block to handle reset.

3

Fix synthesis warning about inferred latches

Sometimes synthesis tools warn about inferred latches if all cases are not covered. To fix this, add an else branch that assigns count to itself if no other condition matches. Update the always block accordingly.

Verilog

module counter(input clk, input reset, output reg [1:0] count);
    always @(posedge clk) begin
        // Add else branch to fix latch warning
        // Your code here
    end
endmodule

Hint

Use else if and else branches to cover all cases and avoid latches.

4

Display a message confirming the fix

Add a initial block that prints "Synthesis warning fixed: no inferred latches." when simulation starts.

Verilog

module counter(input clk, input reset, output reg [1:0] count);
    always @(posedge clk) begin
        if (reset) begin
            count <= 0;
        end else if (count < 2'b11) begin
            count <= count + 1;
        end else begin
            count <= 0;
        end
    end

    // Your code here
endmodule

Hint

Use an initial block with $display to print the message once at simulation start.

Practice

1. What is the main reason synthesis tools generate warnings about incomplete case statements in Verilog?

easy

A. Because the case statement is inside an always block.

B. Because the syntax of the case statement is incorrect.

C. Because the tool does not support case statements.

D. Because not all possible input cases are covered, which may cause unintended hardware behavior.

Solution

1. Step 1: Understand synthesis warnings for case statements

   Synthesis tools warn when a case statement does not cover all possible input values, which can cause unintended latches or hardware behavior.

2. Step 2: Reason why incomplete coverage is problematic

   If some input values are not handled, the hardware may hold previous values or behave unpredictably, which is why the tool warns.

3. Final Answer:

   Because not all possible input cases are covered, which may cause unintended hardware behavior. -> Option D

4. Quick Check:

   Incomplete case coverage = synthesis warning [OK]

Hint: Always cover all input cases in case to avoid warnings [OK]

Common Mistakes:

• Thinking syntax errors cause incomplete case warnings
• Ignoring default cases in case statements
• Assuming tools don't check for all input values

2. Which of the following Verilog code snippets will NOT cause a synthesis warning about unassigned signals?

easy

A. module example(input clk, input a, output reg q); always @(posedge clk) q <= a; endmodule

B. module example(input clk, input a, output reg q); always @(posedge clk) ; endmodule

C. module example(input clk, input a, output reg q); reg temp; always @(posedge clk) temp <= a; endmodule

D. module example(input clk, input a, output reg q); reg temp; always @(posedge clk) q <= temp; endmodule

Solution

1. Step 1: Identify unassigned signals in each snippet

   module example(input clk, input a, output reg q); always @(posedge clk) q <= a; endmodule assigns q on clock edge, so no unassigned output. module example(input clk, input a, output reg q); always @(posedge clk) ; endmodule has an empty always block, so q is never assigned. module example(input clk, input a, output reg q); reg temp; always @(posedge clk) temp <= a; endmodule assigns temp but q is unassigned output. module example(input clk, input a, output reg q); reg temp; always @(posedge clk) q <= temp; endmodule assigns q from temp, but temp is never assigned.

2. Step 2: Determine which code avoids unassigned signals

   Only module example(input clk, input a, output reg q); always @(posedge clk) q <= a; endmodule properly assigns the output q and has no unassigned signals, so no synthesis warning.

3. Final Answer:

   module example(input clk, input a, output reg q); always @(posedge clk) q <= a; endmodule -> Option A

4. Quick Check:

   All outputs assigned = no warnings [OK]

Hint: Check if all outputs get assigned in every clock cycle [OK]

Common Mistakes:

• Ignoring that outputs must be assigned to avoid warnings
• Assuming internal regs cause warnings if unassigned
• Confusing blocking and non-blocking assignments

3. Given the following Verilog code, what synthesis warning will most likely appear?

module test(input wire [1:0] sel, output reg out);
  always @(*) begin
    case(sel)
      2'b00: out = 1'b0;
      2'b01: out = 1'b1;
      // Missing cases for 2'b10 and 2'b11
    endcase
  end
endmodule

medium

A. Warning about incomplete case statement causing inferred latch.

B. Warning about unused input sel.

C. Warning about multiple drivers for out.

D. No warnings; code is synthesizable as is.

Solution

1. Step 1: Analyze the case statement coverage

   The case covers only 2 of 4 possible values of sel. Missing 2'b10 and 2'b11 cases.

2. Step 2: Understand synthesis implications of missing cases

   Because not all cases are covered and no default is provided, synthesis infers a latch to hold out value for missing cases, causing a warning.

3. Final Answer:

   Warning about incomplete case statement causing inferred latch. -> Option A

4. Quick Check:

   Incomplete case = inferred latch warning [OK]

Hint: Add default case to avoid inferred latch warnings [OK]

Common Mistakes:

• Assuming no warning if some cases are missing
• Confusing unused input warnings with case coverage
• Ignoring latch inference from incomplete cases

4. Identify the synthesis warning and fix in the following Verilog snippet:

module fixme(input clk, input a, output reg q);
  reg temp;
  always @(posedge clk) begin
    temp <= a;
  end
  always @(posedge clk) begin
    q <= temp;
  end
endmodule

medium

A. Warning: Unused signal temp. Fix: Remove temp and assign q directly.

B. No synthesis warnings; code is correct.

C. Warning: temp is assigned but never used. Fix: Connect temp to output.

D. Warning: Multiple drivers for q. Fix: Use only one always block for q.

Solution

1. Step 1: Check signal usage and assignments

   temp is assigned from a on clock edge, then q is assigned from temp on next clock edge. Both signals are used properly.

2. Step 2: Verify if multiple drivers or unused signals exist

   Only one always block drives temp, and one drives q. No multiple drivers or unused signals.

3. Final Answer:

   No synthesis warnings; code is correct. -> Option B

4. Quick Check:

   All signals assigned and used properly = no warnings [OK]

Hint: Check if every assigned signal is used and driven once [OK]

Common Mistakes:

• Assuming temp is unused because it is intermediate
• Thinking multiple always blocks cause multiple drivers if signals differ
• Ignoring proper signal flow over clock cycles

5. You have a combinational always block with multiple outputs, but synthesis warns about inferred latches. How can you fix this warning effectively?

hard

A. Add more inputs to the sensitivity list of the always block.

B. Remove the always block and use continuous assignments instead.

C. Add a default assignment to all outputs at the start of the always block.

D. Declare all outputs as wires instead of regs.

Solution

1. Step 1: Understand why inferred latches occur in combinational blocks

   If outputs are not assigned in all possible paths, synthesis infers latches to hold previous values, causing warnings.

2. Step 2: Fix by adding default assignments

   Assign default values to all outputs at the start of the always block to ensure they are always driven, preventing latch inference.

3. Final Answer:

   Add a default assignment to all outputs at the start of the always block. -> Option C

4. Quick Check:

   Default assignments prevent inferred latches [OK]

Hint: Initialize outputs at block start to avoid latches [OK]

Common Mistakes:

• Thinking sensitivity list affects latch warnings
• Assuming changing output type fixes latch inference
• Removing always block without replacing logic