skills.rest
NVIDIA
NVIDIAOFFICIAL
Explore all skills by this author →
WebsiteGitHub

hsb-ip-packetizer

Choose and explain HSB Sensor RX packetizer fields for HOLOLINK_def.svh SystemVerilog configurations.

3.2k|370|Updated Feb 25, 2026
Search Tags:#Configuration#rtl#systemverilog#FPGA#holoscan#sensor bridge#packetizer
One-click install
npx skills add https://github.com/NVIDIA/skills --skill hsb-ip-packetizer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hsb-ip-packetizer
Source: https://github.com/NVIDIA/skills/tree/main/skills/hsb-ip-packetizer
Command: npx skills add https://github.com/NVIDIA/skills --skill hsb-ip-packetizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

FPGA engineers configuring the NVIDIA Holoscan Sensor Bridge must correctly derive packetizer-related fields in HOLOLINK_def.svh, where wrong values for virtual ports, sort resolution, or cycle counts silently break Sensor RX data manipulation. This Skill derives those fields from the user's actual data layout instead of guesswork.

Core Features & Use Cases

  • Packetizer Field Derivation: Computes SIF_RX_PACKETIZER_EN, SIF_RX_VP_COUNT, SIF_RX_SORT_RESOLUTION, SIF_RX_VP_SIZE, and SIF_RX_NUM_CYCLES arrays from stated RX widths and data manipulation intent, with RTL-derived constraint checks.
  • Three Output Modes: Standalone SystemVerilog blocks for direct SVH insertion, labeled packetizer_profile_overlay YAML for handoff to the hsb-ip-def skill, and explanation mode for field semantics and architecture questions.
  • Live Source Awareness: Prefers live HSB IP RTL (rev 16'h2604, backward-compatible with 16'h2603) over bundled references and warns on unknown revisions.
  • Use Case: Given a 512-bit RX0 that must split into four 128-bit virtual streams and a pass-through RX1, the Skill emits enable [1, 0], VP count [4, 1], VP size [128, 32], and matching peer arrays with bypass placeholders.

Quick Start

Ask the agent to use hsb-ip-packetizer to choose packetizer fields for your Sensor RX interfaces, describing each interface's width and whether it needs splitting, rearrangement, replication, or pass-through.

Frequently Asked Questions about hsb-ip-packetizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose HOLOLINK_def.svh packetizer fields for Holoscan Sensor Bridge?▼

Provide the number of Sensor RX interfaces, each interface's SIF_RX_WIDTH, and the intended data manipulation such as splitting into virtual streams or rearranging lanes. The Skill derives SIF_RX_PACKETIZER_EN, VP_COUNT, SORT_RESOLUTION, VP_SIZE, and NUM_CYCLES arrays from those facts and emits them as SystemVerilog localparams.

How do I split a Sensor RX input into multiple virtual streams?▼

State the RX input width and the number of virtual streams needed. For an equal contiguous split of a 512-bit word into four streams, the Skill sets SIF_RX_VP_COUNT to 4 and SIF_RX_VP_SIZE to 128, using the RX width as sort resolution to disable the sort network when no reordering is needed.

What is the difference between hsb-ip-packetizer and hsb-ip-def?▼

hsb-ip-packetizer owns only the five packetizer fields of HOLOLINK_def.svh, while hsb-ip-def handles whole-file generation, validation, and non-packetizer macros. In a handoff, the packetizer skill emits a packetizer_profile_overlay YAML that hsb-ip-def merges and validates.

Which HSB IP revisions does the packetizer configuration support?▼

The bundled references document HSB IP rev 16'h2604 and are backward-compatible with rev 16'h2603. When live HSB IP source is available in the workspace, the Skill prefers the live RTL and warns if the revision is unknown or disagrees with the references.

Can this skill generate runtime APB pattern-RAM programming?▼

No, runtime APB pattern-RAM programming is outside the v1 scope. The Skill only chooses compile-time HOLOLINK_def.svh fields that size and enable packetizer hardware; runtime software still controls pattern RAM, virtual-port selection, bypass, and latency.

Do I need packetizer fields if SENSOR_RX_IF_INST is disabled?▼

No, packetizer fields apply only to Sensor RX interfaces. When SENSOR_RX_IF_INST is undefined or zero, no packetizer arrays are emitted and no packetizer hardware is configured.

Related Skills

Explore More Software Engineering Skills→
johnlindquistjohnlindquist
8

badger-hardware

Configure GPIO, I2C, and SPI for external hardware on Badger 2350.

Community
Intermediate
amoslee2026amoslee2026
41

bb-invoke-qrouter

Detail-route placed DEF files using QRouter to produce routed DEF.

Community
Intermediate
sayalinvidiasayalinvidia

hsb-app

Discover, filter, and execute Holoscan Sensor Bridge applications on a connected devkit via SSH.

Community
Advanced
scitixscitix
225

pod-ping-gateway

Ping the default gateway for a network interface within a pod's network namespace.

Official
Intermediate