Hsb Ip Def
NVIDIAOfficialCreated by Holoscan TeamDistributed by NVIDIA
- Skill
- Tool integration
- Software development
- Apache-2.0
- Medium risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The hsb-ip-def skill provides a structured approach to managing SystemVerilog configuration macros for the Holoscan Sensor Bridge (HSB) IP. It enables users to generate, validate, explain, and compare HOLOLINK_def.svh files, ensuring that macro definitions align with board-level requirements and IP constraints. The skill leverages bundled Python scripts to perform these operations, providing a reliable interface for configuring HSB IP revisions 16'h2603 and 16'h2604.
What it does
- Generates HOLOLINK_def.svh files based on user-confirmed board requirements.
- Validates existing configuration files using a dedicated linting script.
- Explains macro semantics, legal values, and their impact on top-level ports.
- Compares two configuration files to identify semantic differences.
- Provides warnings for potential configuration footguns, such as HD-W3xx issues.
- Integrates with other HSB skills for top-level wrapper creation and packetizer derivation.
When to use it
- When you need to create a new HOLOLINK_def.svh file for a custom HSB board design.
- When you need to verify that an existing configuration file is valid and follows IP constraints.
- When you need to understand the effect of specific macros on the HSB IP dataplane or clocking.
- When you need to diff two configurations to understand changes between board revisions.
Advantages
- Ensures configuration consistency through automated validation.
- Prevents common configuration errors with built-in rule checking.
- Provides clear, grounded explanations for complex macro interactions.
- Maintains compatibility with specific HSB IP revisions.
Usage examples
- “Generate a new HOLOLINK_def.svh for a high-bandwidth single-sensor board.”
- The agent will initiate the generation workflow, asking for board requirements one by one, building a profile, and running the generation script upon confirmation.
- “Validate my current HOLOLINK_def.svh and check for any warnings.”
- The agent will run the validation script, report any errors or warnings, and specifically highlight any HD-W3xx footgun warnings.
- “Is it legal to set HOST_WIDTH=512 and PTP_CLK_FREQ=90_000_000?”
- The agent will use the validation script or macro references to determine if the combination is legal and explain the reasoning.
- “Compare my local def file with the baseline configuration.”
- The agent will run the comparison script and provide a summary of the semantic differences between the two files.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/nvidia/hsb-ip-def/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip hsb-ip-def.zip -d .agents/skills
Documentation by Holoscan Team
HSB IP Def Skill
Purpose
Use this skill through four workflows:
Generate a
HOLOLINK_def.svhfrom confirmed board requirements.Validate an existing def file with the bundled validator.
Explain / Reason about HSB IP macros, legality, and macro-driven ports.
Compare two def files semantically.
Scope
This skill owns the contents of HOLOLINK_def.svh: \definedirectives,localparamarrays, theHOLOLINK_pkgwrapper, and boot-timeinit_reg[]sequence. The surrounding top-level wrapper is owned byhsb-ip-create-top; packetizer-only profile derivation can be delegated to hsb-ip-packetizer`.
The file must use the standard guard plus package HOLOLINK_pkg wrapper. Load references/macro-reference.md for the full wrapper requirement and per-macro semantics.
Prerequisites
Python 3.9+ is required for the bundled scripts; PyYAML is required when reading YAML profiles.
The user must confirm file writes and shell commands unless they already asked for that exact operation.
A concrete def file path, pasted content, or confirmed generation profile is required before script-backed validation or generation.
Live HSB IP source is optional but preferred when validating against a specific checked-out IP revision.
Instructions
Run bundled script preflight from
references/script-usage.mdbefore Generate, Validate, Compare, or script-backed legality checks.Never silently default a macro during Generate. Show the proposed value or inferred requirement and get user confirmation.
Ask one requirements question per turn during chat-driven Generate.
Use sensor-agnostic language unless the user says the design is camera-specific.
Avoid unsupported "typical", "common", "most designs", or corpus-frequency claims. Anchor choices to IP behavior, documented constraints, or user requirements.
Always surface HD-W3xx footgun warnings, even when the user asks only about errors.
Do not generate
FPGA_top.sv; offer handoff tohsb-ip-create-topafter a generated def file is validated.Treat unfamiliar macros as project-specific unless they are documented in this skill's references or live HSB IP source.
Security Considerations
This skill can read and write local files and run shell commands through its bundled scripts. Before running a command or writing a file, state the command or path and get user confirmation unless the user already explicitly requested that exact operation. For pasted HOLOLINK_def.svh content, write only to a safely generated file in an isolated temporary directory and remove it after validation unless the user asks to keep it.
Version, Compatibility, And Live Source
This skill targets HSB IP rev 16'h2604 and is backward-compatible with 16'h2603. Live HSB IP source supersedes bundled references.
When source-sensitive behavior matters:
Locate
<hsb-ip-root>/top/HOLOLINK_top.sv. Known roots includehw/nvcpu_dgx_fpga/vrtl/hololink/and public-releasefpga/nv_hsb_ip/.Read
HOLOLINK_REVandHOLOLINK_BACKWARD_COMPAT_REV.Trust live source for consumed macros, port gates, and RTL behavior when it differs from bundled references.
Pass
--ip-source <root>toscripts/validate_def.pywhen validating against a known source root.
Public-doc baseline:
https://github.com/nvidia-holoscan/holoscan-sensor-bridge/blob/release-2.6.0-EA/docs/user_guide/ip_integration.mdhttps://github.com/nvidia-holoscan/holoscan-sensor-bridge/blob/release-2.6.0-EA/docs/user_guide/port_description.md
Workflow Decision
Generate when the user asks to create, scaffold, draft, design, or produce a
HOLOLINK_def.svh.Validate when the user asks to lint, check, validate, or review a
HOLOLINK_def.svh.Explain / Reason when the user asks what a macro does, whether a combination is legal, why validation fails, or how a macro affects
HOLOLINK_top.Compare when the user asks to diff two def files or understand what changed between configurations.
Generate
Load references/generate-workflow.md and references/script-usage.md.
Follow the detailed Generate workflow in the reference: run preflight, classify supplied requirements, ask one requirements question per turn, build a flat YAML profile, run scripts/generate_def.py, show provenance for generated fields, and offer handoff to hsb-ip-create-top.
When packetizer fields are needed, invoke hsb-ip-packetizer with the known RX count, RX widths, and the user's data-manipulation description. Consume only that skill's packetizer_profile_overlay YAML keys, merge them into the in-progress profile, and continue full-file generation and validation here.
Validate
Load references/script-usage.md. Load references/validation-rules.md only when explaining specific rule IDs or validation behavior.
Steps:
Run bundled script preflight once per session.
Locate the file. If the user pastes content, tell them the generated temporary path before writing, ask for confirmation, use an isolated safe temp path, and clean it up after validation unless they ask to keep it. Otherwise use the provided path.
Run
<PY> scripts/validate_def.py <path> --jsonand do not reimplement validation in context.Group findings by severity: errors, warnings, then info. For each error, cite rule ID, line number, and macro when available.
Always surface footgun warnings, especially HD-W3xx silent-fallback warnings.
If clean, confirm the inferred archetype and IP version, then suggest the likely next check or handoff.
Explain / Reason
Load only the reference needed for the question:
| Question type | Reference |
|---|---|
| Macro semantics or legal values | references/macro-reference.md |
| Validation rule behavior | references/validation-rules.md |
| Macro-driven port effects | references/top-port-map.md |
init_reg[] and N_INIT_REG | references/init-reg-cookbook.md |
| Advanced macros | references/advanced-macros.md |
| Example legal configurations | references/archetypes.md |
For grounded legality questions, run preflight and prefer validating a concrete file or minimal synthetic file with scripts/validate_def.py over hand reasoning. Cite RTL line ranges from references when explaining why a rule exists.
Compare
Load references/script-usage.md, run preflight, then use <PY> scripts/compare_defs.py <a.svh> <b.svh> [--json|--text]. Summarize semantic differences, not whitespace or comment-only changes.
Limitations
Do not generate
FPGA_top.sv; usehsb-ip-create-topafter the defs file validates.Do not derive packetizer-only field sets here when the packetizer behavior is underspecified; delegate that slice to
hsb-ip-packetizer.Do not treat bundled archetypes or corpus metadata as norms. They are examples and maintenance metadata, not defaults.
Do not silently accept unknown macros as validated HSB IP behavior unless live source or references document them.
Troubleshooting
Script preflight fails: report the missing Python or PyYAML requirement and stop before generation or validation.
Validation reports errors: group by severity, cite rule ID and line, and fix the defs file before offering top-level handoff.
Validation reports HD-W3xx warnings: surface them even when there are no errors because they describe silent RTL fallback risks.
Unknown macro appears: treat it as project-specific unless live HSB IP source or bundled references document it.
Available Scripts
Use <PY> selected during preflight from references/script-usage.md for every command.
| Script | Purpose | Arguments |
|---|---|---|
scripts/generate_def.py | Generate HOLOLINK_def.svh from an archetype and/or YAML/JSON profile; validates before writing | --profile <path>, --archetype <slug>, -o <output>, optional --allow-random-uuid compatibility flag |
scripts/validate_def.py | Validate a HOLOLINK_def.svh and emit JSON or text findings | <path/to/HOLOLINK_def.svh>, optional --json or --text, optional --ip-source <root> |
scripts/compare_defs.py | Compare two def files semantically, ignoring whitespace/comment-only changes | <a.svh> <b.svh>, optional --json or --text |
scripts/build_corpus_metadata.py | Maintenance helper to rebuild anonymized corpus metadata; do not run during normal user workflows | <path1> [<path2> ...] |
Bundled Resources
| Resource | Use |
|---|---|
references/generate-workflow.md | Detailed Generate workflow, requirement order, question style, and per-topic prompt guidance |
references/script-usage.md | Preflight, command forms, and run_script() examples for bundled scripts |
references/macro-reference.md | Wrapper requirement, macro semantics, legal constraints, and RTL citations |
references/validation-rules.md | Rule catalog for validator findings |
references/archetypes.md | Illustrative legal configurations; never treat as templates or frequency guidance |
references/init-reg-cookbook.md | Boot-time APB write sequence patterns and address conventions |
references/top-port-map.md | Macro-to-HOLOLINK_top port effects |
references/advanced-macros.md | SYNC_CLK_HIF_APB, SYNC_CLK_HIF_PTP, PERI_RAM_DEPTH, and DISABLE_COE |
assets/metadata/corpus.json, assets/metadata/corpus-stats.json | Maintenance metadata only; do not cite corpus counts as user guidance |
scripts/generate_def.py | Generate a def file from a profile |
scripts/validate_def.py | Validate a def file and emit JSON/text findings |
scripts/compare_defs.py | Compare two def files semantically |
Examples
Use hsb-ip-def to generate a HOLOLINK_def.svh for a new HSB board.Treat as Generate, run script preflight, classify supplied requirements, ask one requirement question per turn, and runscripts/generate_def.pyonly after the profile is confirmed.Use hsb-ip-def to validate my existing HOLOLINK_def.svh and tell me whether any warnings are important.Treat as Validate, ask for or locate the file, runscripts/validate_def.py <path> --json, group findings by errors, warnings, and info, and always surface HD-W3xx footgun warnings.Use hsb-ip-def to explain whether HOST_WIDTH=512 and PTP_CLK_FREQ=90_000_000 is legal.Treat as Explain / Reason, prefer a concrete validator-backed check over hand reasoning, and load only the macro or validation reference needed to explain the result.
Files
- ATTRIBUTION.mdAdded by AutoGineer895 B
- BENCHMARK.md3.4 KiB
- LICENSELicence file added by AutoGineer11.2 KiB
- README.md5.0 KiB
- SKILL.md11.3 KiB
- assets/metadata/corpus-stats.json5.3 KiB
- assets/metadata/corpus.json16.9 KiB
- evals/evals.json4.4 KiB
- references/advanced-macros.md4.7 KiB
- references/archetypes.md22.3 KiB
- references/generate-workflow.md25.1 KiB
- references/init-reg-cookbook.md5.7 KiB
- references/macro-reference.md29.8 KiB
- references/script-usage.md3.1 KiB
- references/top-port-map.md10.2 KiB
- references/validation-rules.md14.8 KiB
- scripts/build_corpus_metadata.pyScript7.5 KiB
- scripts/compare_defs.pyScript6.0 KiB
- scripts/generate_def.pyScript8.6 KiB
- scripts/lib/__init__.pyScript0 B
- scripts/lib/emitter.pyScript25.7 KiB
- scripts/lib/parser.pyScript22.3 KiB
- scripts/lib/rules.pyScript29.1 KiB
- scripts/validate_def.pyScript5.6 KiB
- skill-card.md4.5 KiB
- skill.oms.sig8.9 KiB
scripts/generate_def.py
#!/usr/bin/env python3
"""Generate a HOLOLINK_def.svh file from a profile (and optional archetype defaults).
Usage:
generate_def.py --profile <path> [-o <output>]
generate_def.py --archetype <slug> [--profile <path>] [-o <output>]
The --profile argument accepts YAML or JSON (auto-detected by extension).
If no `uuid:` is supplied, the generator creates a random 128-bit UUID and
prints a NOTE to stderr — pin a specific value by adding `uuid:` to your
profile. If neither --archetype nor a profile `archetype:` key is given,
generic per-macro defaults are used and the user's profile fully specifies
the design.
The generator validates the emitted file with validate_def.py before writing.
If validation fails, the file is NOT written and the validator's errors are
printed to stderr.
Profile schema (top-level keys, all optional):
archetype: "<slug>" # optional; one of the 5 example archetypes
uuid: "128'h…" # board-specific 128-bit hex literal; auto-generated if missing
hif_clk_freq: <int Hz>
apb_clk_freq: <int Hz>
ptp_clk_freq: <int Hz>
enum_eeprom: <bool>
eeprom_reg_addr_bits: 8 | 16
datapath_width: <int>
datauser_width: 1 | 2
sensor_rx_count: <int|null>
sif_rx_data_gen: <bool>
sif_rx_widths: [<int>, …] # length must match sensor_rx_count
sif_rx_packetizer_en: [0|1, …]
sif_rx_vp_count: [<int>, …]
sif_rx_sort_resolution: [<int>, …]
sif_rx_vp_size: [<int>, …]
sif_rx_num_cycles: [<int>, …]
sensor_tx_count: <int|null>
sif_tx_widths: [<int>, …]
sif_tx_buf_size: [<int>, …] # depth in SIF_TX_WIDTH elements
host_width: <int>
host_if_inst: <int>
host_mtu: <int>
spi_inst: <int|null>
i2c_inst: <int|null>
uart_inst: <int|null>
gpio_inst: <int>
gpio_reset_value: "<SystemVerilog literal>"
reg_inst: <int>
init_reg: [] | [{addr: "32'h…", data: "32'h…"}, …]
ext_ptp: <bool>
sync_clk_hif_apb: <bool>
sync_clk_hif_ptp: <bool>
peri_ram_depth: <int|null>
disable_coe: <bool>
Exit codes:
0 generated file passes validation
1 generated file fails validation
2 profile / argument error
"""
import argparse
import json
import secrets
import subprocess
import sys
import tempfile
from pathlib import Path
from typing import Any, Dict, List, Optional, Tuple
UUID_BITS = 128
UUID_HEX_LENGTH = 32
UUID_HEX_GROUP_SIZE = 4
EXIT_SUCCESS = 0
EXIT_VALIDATION_ERROR = 1
EXIT_USAGE_ERROR = 2
def _resolve_lib_path() -> None:
here = Path(__file__).resolve().parent
if str(here) not in sys.path:
sys.path.insert(0, str(here))
_resolve_lib_path()
from lib.emitter import ARCHETYPE_DEFAULTS, build_profile, emit_svh # noqa: E402
def _load_profile(path: Path) -> Dict[str, Any]:
text = path.read_text()
if path.suffix.lower() == ".json":
return json.loads(text)
try:
import yaml # type: ignore
except ImportError:
sys.stderr.write("ERROR: PyYAML is required for YAML profiles. "
"Install with `pip install pyyaml` or use a .json profile.\n")
sys.exit(EXIT_USAGE_ERROR)
return yaml.safe_load(text) or {}
def _normalize_init_reg(init_reg: Any) -> Optional[List[Tuple[str, str]]]:
"""Accept init_reg as either:
- [] to suppress system init
- list of [addr, data] pairs
- list of {"addr": "...", "data": "..."} dicts
"""
if init_reg is None:
return None
out: List[Tuple[str, str]] = []
for entry in init_reg:
if isinstance(entry, dict):
out.append((str(entry["addr"]), str(entry["data"])))
elif isinstance(entry, (list, tuple)):
try:
addr, data = entry
except ValueError as exc:
raise ValueError(f"init_reg entry has unexpected form: {entry!r}") from exc
out.append((str(addr), str(data)))
else:
raise ValueError(f"init_reg entry has unexpected form: {entry!r}")
return out
def _generate_random_uuid() -> str:
"""Generate a random 128-bit UUID literal."""
val = secrets.randbits(UUID_BITS)
hex_str = f"{val:0{UUID_HEX_LENGTH}x}"
grouped = "_".join(
hex_str[i:i + UUID_HEX_GROUP_SIZE].upper()
for i in range(0, UUID_HEX_LENGTH, UUID_HEX_GROUP_SIZE)
)
return f"128'h{grouped}"
def main(argv=None) -> int:
ap = argparse.ArgumentParser(
prog="generate_def.py",
description="Generate a HOLOLINK_def.svh from an archetype + overrides.",
)
ap.add_argument("-a", "--archetype",
choices=sorted(ARCHETYPE_DEFAULTS.keys()),
help="Optional. If omitted and the profile has no `archetype:` key, "
"generic per-macro defaults are used.")
ap.add_argument("-p", "--profile", type=Path,
help="YAML or JSON profile file with overrides.")
ap.add_argument("-o", "--output", type=Path, default=None,
help="Output path. Default: print to stdout.")
ap.add_argument("--allow-random-uuid", action="store_true",
help="Deprecated and ignored. Random UUID is generated by "
"default when none is supplied.")
args = ap.parse_args(argv)
overrides: Dict[str, Any] = {}
archetype = args.archetype
if args.profile:
if not args.profile.exists():
print(f"ERROR: profile file not found: {args.profile}", file=sys.stderr)
return EXIT_USAGE_ERROR
try:
overrides = _load_profile(args.profile)
except Exception as e: # noqa: BLE001
print(f"ERROR: failed to load profile: {e}", file=sys.stderr)
return EXIT_USAGE_ERROR
if not isinstance(overrides, dict):
print(f"ERROR: profile must be a mapping, got {type(overrides).__name__}", file=sys.stderr)
return EXIT_USAGE_ERROR
# Profile may name its own archetype
archetype = archetype or overrides.pop("archetype", None)
# archetype is now optional; emitter falls back to GENERIC_DEFAULTS when None.
# Deprecation NOTE for the legacy flag (kept as no-op for back-compat).
if args.allow_random_uuid:
print("NOTE: --allow-random-uuid is deprecated and ignored. "
"Random UUID is generated by default when none is supplied.",
file=sys.stderr)
# Normalize init_reg if present
if "init_reg" in overrides:
try:
overrides["init_reg"] = _normalize_init_reg(overrides["init_reg"])
except Exception as e: # noqa: BLE001
print(f"ERROR: invalid init_reg: {e}", file=sys.stderr)
return EXIT_USAGE_ERROR
# UUID handling: random by default when not supplied. Pin a specific
# value by adding `uuid:` to the profile.
if "uuid" not in overrides or not overrides["uuid"]:
overrides["uuid"] = _generate_random_uuid()
print(f"NOTE: no UUID supplied; generated random UUID {overrides['uuid']}",
file=sys.stderr)
profile, build_notes = build_profile(archetype, overrides)
for note in build_notes:
print(f"NOTE: {note}", file=sys.stderr)
svh_text = emit_svh(profile)
# Validate via subprocess
validator = Path(__file__).resolve().parent / "validate_def.py"
with tempfile.NamedTemporaryFile(mode="w", suffix=".svh", delete=False) as tf:
tf.write(svh_text)
tmp_path = Path(tf.name)
try:
proc = subprocess.run(
[sys.executable, str(validator), str(tmp_path), "--json"],
capture_output=True, text=True, check=False,
)
try:
result = json.loads(proc.stdout)
except json.JSONDecodeError:
print(f"ERROR: validator did not produce valid JSON. stdout:\n{proc.stdout}", file=sys.stderr)
return EXIT_VALIDATION_ERROR
errors = result.get("errors", [])
warnings = result.get("warnings", [])
if errors:
print("ERROR: generated file failed validation. Refusing to write output.", file=sys.stderr)
for e in errors:
print(f" [{e['rule']}] line {e['line']} {e.get('macro') or '—'}: {e['msg']}", file=sys.stderr)
return EXIT_VALIDATION_ERROR
if warnings:
print(f"NOTE: {len(warnings)} warning(s) from validator (not blocking):", file=sys.stderr)
for w in warnings:
print(f" [{w['rule']}] line {w['line']} {w.get('macro') or '—'}: {w['msg']}", file=sys.stderr)
finally:
tmp_path.unlink(missing_ok=True)
# Write output
if args.output:
args.output.write_text(svh_text)
print(f"Wrote {args.output}", file=sys.stderr)
else:
sys.stdout.write(svh_text)
return EXIT_SUCCESS
if __name__ == "__main__":
sys.exit(main())
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Python
The author says: Targets HSB IP rev 16'h2604; backward-compatible with 16'h2603 (the public release rev). Prefer live HSB IP source when available; warn on unknown revisions. Requires Python 3.9+ with PyYAML for the generator.
Security
What our scanner noticed· Medium risk
- Large base64-encoded blobs
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- Holoscan Team
- Publisher
- NVIDIA (Official)
- Distributed by
- NVIDIA
- Source
- NVIDIA/skills · skills/hsb-ip-def · commit fce3cca
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE-APACHE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Holoscan Team or NVIDIA.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download hsb-ip-def.zip