domains / families / software-engineering / hsb-ip-def
hsb-ip-def
separate
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.
When to use
- **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.
- This skill owns the contents of `HOLOLINK_def.svh`: `\`define` directives, `localparam` arrays, the `HOLOLINK_pkg` wrapper, and boot-time `init_reg[]` sequence. The surrounding top-level wrapper is owned by `hsb-ip-create-top`; packetizer-…
When not to use
- Do not generate `FPGA_top.sv`; use `hsb-ip-create-top` after 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.
Skill page
Source