verilog-basics-for-lowlevel

Verilog Basics for Low-Level Engineers

Purpose

Give firmware and kernel engineers enough Verilog/SystemVerilog literacy to read RTL: modules, clocks/resets, combinational vs sequential logic, bus interfaces, and why hardware behavior explains driver bugs — not a replacement for HDL design courses.

When to Use

• Reference manual unclear — RTL clarifies register behavior
• Understanding CDC (clock domain crossing) bugs
• Correlating DMA/AXI transactions with driver ordering
• Reviewing SoC block diagram with hardware team

Workflow

1. Module structure

module uart_tx (
    input  wire       clk,
    input  wire       rst_n,   /* active-low async reset */
    input  wire

wire = combinational/network; reg in always block = flip-flop unless combinational always @(*).

2. Synthesizable subset (what firmware folks need)

Avoid #delay in synthesizable RTL — simulation only.

3. Reset discipline

• Async assert, sync deassert common (rst_sync_n)
• Firmware must wait post-reset setup times — see RM reset chapter
• Multiple reset domains → peripheral may need explicit soft reset bit

4. Bus protocols (reading SoC diagrams)

Linux regmap MMIO maps to APB/AXI slave decode in RTL address map.

5. Clock domains

Signals crossing clk_a → clk_b need synchronizers (2+ FFs). Metastability causes intermittent firmware bugs — not fixed in software alone.

6. Simulation vs silicon

QEMU/peripheral models may not match RTL edge cases.

7. Agent usage

Common Problems

Related Skills

• skills/baremetal/mmio-and-bit-manipulation — register access from C
• skills/baremetal/peripherals-from-datasheet — RM ↔ RTL
• skills/baremetal/datasheet-and-refmanual-reading — doc navigation
• skills/kernel-dev/device-tree — hardware integration in Linux
• skills/qemu/protocol-analysis — validate bus timing