hsb-ip-def

name	hsb-ip-def
author	Holoscan Team <[e-mail]>
description	Generate, validate, compare, or explain HSB HOLOLINK_def.svh macros. Do not use for FPGA_top.sv wrappers or packetizer-only derivation. Generation runs bundled Python scripts locally through shell commands and writes validated .svh output files after user-confirmed paths.
version	0.1.0
tags	["holoscan","hsb","fpga","systemverilog","configuration"]
permissions	["file_read","file_write","shell"]
license	Apache-2.0
compatibility	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.
metadata	{"author":"Holoscan Team <[e-mail]>","team":"holoscan","domain":"fpga","vendor":"nvidia","tags":["holoscan","hsb","fpga","systemverilog","configuration"],"languages":["systemverilog","python"],"artifact":"HOLOLINK_def.svh","hsb_ip_version":"16'h2604","min_compat_rev":"16'h2603"}

HSB IP Def Skill

Purpose

Use this skill through four workflows:

• Generate a HOLOLINK_def.svh from 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.md before 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 to hsb-ip-create-top after 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