mcpField
V
verilog-basics-for-lowlevel

verilog-basics-for-lowlevel

github.com/mohitmishra786Development269274 installsUpdated 18w ago
Repository

About verilog-basics-for-lowlevel

A learning skill for firmware and kernel engineers who need to read Verilog/SystemVerilog RTL. It focuses on clocks, resets, buses, and how hardware behavior can explain driver bugs, rather than teaching HDL design.

Key features

  1. 01Understand modules and sequential logic
  2. 02Recognize reset and clock-domain issues
  3. 03Read APB, AHB, and AXI interfaces
  4. 04Connect RTL behavior to drivers

Use cases

  1. 01Clarify register behavior from RTL
  2. 02Investigate clock-domain crossing bugs
  3. 03Trace DMA/AXI transactions against driver ordering

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel

After installing, type/verilog-basics-for-lowlevelin Claude Code to confirm it loaded.

Details

From the project README

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       start,
    input  wire [7:0] data,
    output reg        busy
);
    /* sequential logic */
    always @(posedge clk or negedge rst_n) begin
        if (!rst_n)
            busy <= 1'b0;
        else if (start)
            busy <= 1'b1;
        /* ... */
    end
endmodule

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

2. Synthesizable subset (what firmware folks need)
ConstructMeaning
posedge clkRegistered update
assign x = a & bCombinational
case / if in always @(*)Mux logic
Parameters #(.WIDTH(32))Configurable width

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)
BusTypical use
APBSlow peripherals, simple reg interface
AHBHigher throughput on-chip
AXIDMA, modern SoCs — bursts, channels

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
# Typical open-source sim (conceptual)
iverilog -o sim.vvp design.v tb.v
vvp sim.vvp

QEMU/peripheral models may not match RTL edge cases.

7. Agent usage
/verilog-basics-for-lowlevel Explain this APB register block and when STATUS bit updates relative to WRITE

Common Problems

SymptomCauseFix
Bit toggles oncePulse in RTLPoll latch / clear-on-read in driver
Random corruptionCDCHardware synchronizer; don't hack delays
Read stale dataBus bridge bufferFollow RM ordering / barrier
IRQ stuckLevel vs pulse in RTLMatch handler ACK sequence
Verilog vs VHDLMixed SoC docsFocus on interface signals table

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

Comments

Markdown supported