uart-harness

Estrellas17

Forks3

Actualizado24 de julio de 2026 a las 01:23

The UART characterization-harness methodology - one host program running identically against cocotb sim and the FPGA. Sim transport, regmap-by-name, board bring-up gotchas (JTAG serials, ttyUSB). Use for any board characterization flow.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

sean-galloway

sean-galloway/RTLDesignSherpa

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Ingenieros electrónicos (excepto computadoras)Arquitectura e ingeniería·SOC 17-2072

SKILL.md

readonly

name	uart-harness
description	The UART characterization-harness methodology - one host program running identically against cocotb sim and the FPGA. Sim transport, regmap-by-name, board bring-up gotchas (JTAG serials, ttyUSB). Use for any board characterization flow.

uart-harness

READ FIRST: vault/handbook/fpga/uart-harness.md (the handbook is the repo's memory; this skill is the signpost). One host program, sim + silicon; registers by name only. Board mechanics: vault/handbook/fpga/boards.md.

The handbook root is vault/handbook/INDEX.md - design/, dv/, fpga/ areas, atomic notes, wikilinked. When you learn a durable lesson in this domain, ADD IT TO THE HANDBOOK NOTE, not to this skill.

Más de este repositorio

mismo repositorio

module-docs

sean-galloway/RTLDesignSherpa

Authoring a per-module reference page under docs/markdown (RTLCommon/RTLMath/RTLAmba) - the local .md style (header table, Overview, Architecture, Top-level Interface, Data model, Timing, Related, Test) and the SV header block that mirrors it. Use whenever you add or change an RTL block and need its docs/markdown page, and keep the book index in sync.

2026-07-2517

doc-placement

sean-galloway/RTLDesignSherpa

What kind of documentation lives where in this repo - handbook (method) vs docs/markdown (reader-facing) vs vault/Tasks (work) vs beside-code (CLAUDE.md, PRD). The rule that a beside-code README is a link, never a standalone guide, and that style guides / how-tos never live in the RTL tree. Use before creating, moving, or "tidying" any .md file, and when reviewing an area's meta-docs.

2026-07-2417

coverage

sean-galloway/RTLDesignSherpa

Coverage methodology - Verilator line/toggle coverage per component, functional coverage expectations, and the monbus packet-type coverage matrix. Use when adding tests, closing coverage, or preparing a board-gate sign-off.

2026-07-2417

doc-methods

sean-galloway/RTLDesignSherpa

The Sherpa documentation pipeline - md_to_docx with --style, LoF/LoT/LoW caption encoding, book indexes, RTL PDF generation, HAS/MAS vs operator guides. Use before generating or restructuring any deliverable doc.

2026-07-2417

filelists

sean-galloway/RTLDesignSherpa

Filelist rules - EVERY module MUST have a .f and MUST be registered in bin/filelists.toml. Components own their compile closure, consumers -f include, never hand-list another area's sources. Use when adding ANY new RTL module, test, or .f file.

2026-07-2417

formal

sean-galloway/RTLDesignSherpa

Formal verification flow - SymbiYosys via sv2v flatten, in-RTL ifdef FORMAL properties, mutation-checking every new assertion, harness vacuity traps. Use when writing properties, regenerating proofs, or after changing any module with a formal dir.

2026-07-2417

Ejecuta cualquier Skill con un clic