Verilog Design Methodologies & Modeling Styles

Each component can be tested independently
Ideal for small or modular projects Example: Design a full-adder first, then build an 8-bit ripple-carry adder from multiple full-adders.

2. Top-Down Design
#

How it works: Begin with a high-level specification or block diagram, then divide it into submodules. Advantages:

Enables early architectural validation
More manageable in large projects Example: Design a CPU starting from the instruction set, then define submodules like ALU and register file.

3. Mixed Design (Hybrid Approach)
#

Real-World Usage: Most common in industry. How it’s done:

Top-level architecture is defined using top-down planning
Critical submodules (e.g., PLLs, memory controllers) are developed bottom-up.

graph TD
  A[Top-Level Spec] --> B[Submodule 1]
  A --> C[Submodule 2]
  B --> D[Gate-Level Implementation]
  C --> E[Third-Party IP]

📝 Verilog Modeling Styles
#

1. Behavioral Modeling
#

Use case: Algorithmic descriptions and control logic
Key constructs:
- always @(*) for combinational logic
- always @(posedge clk) for sequential logic Example:

module max_selector (
    input  [7:0] a,
    input  [7:0] b,
    output [7:0] y
);

    reg [7:0] y_reg;
    assign y = y_reg;

    always @(*) begin
        y_reg = (a > b) ? a : b;
    end

endmodule

2. Dataflow Modeling
#

Typical for: Arithmetic units, multiplexers, buses
Important points:
- assign statements are evaluated continuously
- The left-hand side must be a wire Example:

module mux2to1 (
    input        sel,
    input  [7:0] in1,
    input  [7:0] in2,
    output [7:0] out
);

    assign out = (sel) ? in1 : in2;

endmodule

3. Structural Modeling
#

Real-world analogy: Like wiring components in a schematic
Critical notes:
- Uses module instantiations
- Port mapping can be by name or position Example:

module and_gate (
    input  a,
    input  b,
    output y
);

    assign y = a & b;

endmodule

module top_module (
    input  in1,
    input  in2,
    output out
);

    and_gate U1 (
        .a(in1),
        .b(in2),
        .y(out)
    );

endmodule

4. Gate-Level Modeling
#

Modern use: Mostly handled automatically by synthesis tools
When used:
- ASIC standard cell mapping
- FPGA primitives (e.g., LUTs, DSPs) Example:

module and_gate_delayed (
    input  in1,
    input  in2,
    output out
);

    and #(2) G1 (out, in1, in2); // 2ns delayed AND gate

endmodule

🚀 Design Flow: From Code to Hardware
#

flowchart TD
  A[System Specification] --> B[Behavioral RTL Design]
  B --> C[RTL Simulation & Functional Verification]
  C --> D[Synthesis]
  D --> E[Gate-Level Netlist]
  E --> F[Place & Route]
  F --> G[Bitstream / GDSII Generation]
  G --> H[Timing / Power / DRC / LVS Verification]
  H -->|If Failed| B

This flow represents the typical lifecycle of a Verilog design — starting from behavioral RTL modeling, simulating it, then synthesizing it into gates, placing and routing it physically, and finally generating either a bitstream for FPGA programming or mask data for ASIC fabrication.

Verilog HDL Series - This article is part of a series.

Part 1: Introduction to Verilog: Basics for Digital Design

Part 2: This Article

Part 3: Hardware Design Abstraction Levels in Verilog

Part 4: Verilog Data Types, Logic Values & Arrays Explained

Part 5: Verilog Modules, Ports, Assignments & Best Practices

Part 6: Verilog initial Block: Testbench & Simulation Essentials

Part 7: Verilog Control Flow: if, case, loops & RTL Guidelines

Part 8: Verilog generate Block: Parameterized Hardware Design

Part 9: Verilog Assignments: Procedural vs. Continuous Explained

Part 10: Verilog Blocking vs. Non-Blocking Assignments

Part 11: Verilog Syntax Overview: Essentials for Digital Design