rtl-conformance-test

Compare RTL-generated bitstreams against JM/HM reference decoder outputs.

43|9|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-conformance-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rtl-conformance-test
Source: https://github.com/babyworm/rtl-agent-team/tree/main/skills/rtl-conformance-test
Command: npx skills add https://github.com/babyworm/rtl-agent-team --skill rtl-conformance-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Ensure RTL-encoded bitstreams are bitexact matches against JM/HM (H.264/H.265) reference decoder outputs so that standards compliance is proven prior to tape-out sign-off. This removes ambiguity from functional verification by providing the normative evidence required by codec standards.

Core Features & Use Cases

  • Bitexact comparison tooling: Uses a deterministic byte-by-byte comparator with optional MD5 verification and frame-location calculation to find the first mismatch.
  • Per-vector pass/fail reporting: Runs conformance vectors, records PASS/FAIL per vector in sim/conformance/results.json, and captures mismatch byte offsets and frame locations.
  • Operational guidance & escalation: Enforces testbench naming conventions, selects conformance suites, and defines stop/escalation conditions when JM/HM are missing or many vectors fail.
  • Use case: Run the JVT/JVET conformance suite for a CABAC encoder to validate 100% bitexact output against JM/HM prior to sign-off.

Quick Start

Compare RTL-generated bitstreams in sim/conformance against the JM/HM golden outputs, record per-vector PASS/FAIL, and report the first mismatch byte and frame location.

Frequently Asked Questions about rtl-conformance-test

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

FAQPage Schema
How do I verify RTL codec conformance against JM and HM reference decoders?▼

To verify RTL codec conformance, run per-vector RTL simulations and perform bitexact comparisons against JM/HM reference decoder outputs to prove standards compliance prior to tape-out sign-off.

How does bitexact comparison find the first mismatch in H.264 or H.265 bitstreams?▼

Bitexact comparison uses a deterministic byte-by-byte comparator to find the first mismatch in H.264/H.265 bitstreams, reporting the exact mismatch byte offset and calculating the corresponding frame location.

Can I validate yuv420 frame dimensions and MD5 checksums during conformance testing?▼

Yes, you can validate yuv420 frame dimensions and optionally verify MD5 checksums during conformance testing to ensure the normative evidence required by codec standards is met.

What should I do if many conformance vectors fail or JM/HM reference decoders are missing?▼

If many conformance vectors fail or JM/HM reference decoders are missing, the testing process defines specific stop and escalation conditions to handle missing dependencies and widespread test failures.

How do I generate per-vector PASS or FAIL results for a CABAC encoder?▼

To generate per-vector PASS or FAIL results for a CABAC encoder, run the JVT or JVET conformance suite, recording results in sim/conformance/results.json while capturing mismatch byte offsets and frame locations.