verilog-basics-for-lowlevel — Claude Code skill: what it does
verilog-basics-for-lowlevel — a skill that teaches firmware and kernel engineers to read Verilog RTL: modules, clocking, reset logic, bus protocols. Use it when docs are unclear and hardware behavior explains driver bugs.
MIT 345 installs ★ 298 updated 2026-06-27
npx skills add mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel -a claude-codeWhat verilog-basics-for-lowlevel does
The skill provides the minimum Verilog literacy needed to read RTL. It distinguishes wire from reg, explains always @(posedge clk), APB/AXI/AHB bus interfaces, and clock domain crossing. It walks through common problems: a bit toggles once (pulse in RTL), random data corruption (CDC without synchronizer), stuck IRQ (level vs pulse). Shows how to map reference manual registers to RTL blocks and why QEMU models may diverge from silicon.
Activates on queries about Verilog basics, RTL, clock domain, reset synchronizer, MMU in hardware. Covers synthesizable constructs (posedge, case, width parameters) and explains when firmware must wait for setup time after reset or follow transaction ordering for bus bridges.
Includes a table of synthesizable constructs, module examples with async reset, simulation commands via iverilog. Without reset discipline and inter-domain synchronizers, bugs will be intermittent and cannot be fixed in software alone.
What it helps with
- understand when a register updates relative to an APB write
- debug CDC issues between clock domains
- correlate DMA/AXI transactions with driver operation ordering
- read SoC block diagrams with hardware teams
- explain why STATUS bit changes at a different time than firmware expects
Example prompts for the agent
- Explain this APB register block and when the STATUS bit updates after WRITE
- Why does this RTL code cross
clk_aandclk_bdomains without a synchronizer? - Walk through the
uart_txmodule: which signals are combinational, which are registered
How to install verilog-basics-for-lowlevel
1Skills CLI (Vercel)
npx skills add mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel -a claude-code2Manually: put the files in place
~/.claude/skills/verilog-basics-for-lowlevel/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/verilog-basics-for-lowlevel/
1Skills CLI (Vercel)
npx skills add mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel -a codex2Manually: put the files in place
.agents/skills/verilog-basics-for-lowlevel/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel -a cursor2Manually: put the files in place
.cursor/skills/verilog-basics-for-lowlevel/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install mohitmishra786/low-level-dev-skills skills/qemu/verilog-basics-for-lowlevel2Manually: put the files in place
.github/skills/verilog-basics-for-lowlevel/SKILL.md1Skills CLI (Vercel)
npx skills add mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel -a gemini-cli2Platform CLI
gemini skills install https://github.com/mohitmishra786/low-level-dev-skills --path skills/qemu/verilog-basics-for-lowlevelManually: put the files in place
.devin/skills/verilog-basics-for-lowlevel/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about verilog-basics-for-lowlevel
How to install verilog-basics-for-lowlevel in Claude Code?
Run npx skills add mohitmishra786/low-level-dev-skills --skill verilog-basics-for-lowlevel -a claude-code, the skill lands in ~/.claude/skills/verilog-basics-for-lowlevel/SKILL.md.
What does verilog-basics-for-lowlevel do?
Teaches reading Verilog RTL: distinguishes wire from reg, explains clock/reset logic, APB/AXI buses, CDC. Helps firmware and driver developers understand why hardware behaves differently than the reference manual suggests.
When is the skill needed?
When the reference manual is unclear and RTL clarifies register behavior, when debugging CDC bugs, correlating DMA transactions with driver code, or reviewing SoC diagrams with hardware teams.
Source text
SKILL.md · MIT
---
name: verilog-basics-for-lowlevel
description: Verilog basics skill for firmware and kernel engineers. Use when reading RTL to understand hardware behavior, reset/clock domains, bus protocols, or collaborating with hardware teams. Activates on queries about Verilog basics, RTL, hardware description, clock domain, reset synchronizer, or MMU in hardware.
---
# 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
```verilog
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)
| Construct | Meaning |
|-----------|---------|
| `posedge clk` | Registered update |
| `assign x = a & b` | Combinational |
| `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)
| Bus | Typical use |
|-----|-------------|
| APB | Slow peripherals, simple reg interface |
| AHB | Higher throughput on-chip |
| AXI | DMA, 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
```bash
# 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
| Symptom | Cause | Fix |
|---------|-------|-----|
| Bit toggles once | Pulse in RTL | Poll latch / clear-on-read in driver |
| Random corruption | CDC | Hardware synchronizer; don't hack delays |
| Read stale data | Bus bridge buffer | Follow RM ordering / barrier |
| IRQ stuck | Level vs pulse in RTL | Match handler ACK sequence |
| Verilog vs VHDL | Mixed SoC docs | Focus 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
© mohitmishra786 · MIT · mohitmishra786/low-level-dev-skills