Uploaded September 2026 | Updated November 2026, 4 days ago
Block-level verification of parameterised RTL relies on hand-written parameter sets chosen from designer intent, not the assembled design. As the SoC grows, the two drift, and that gap goes undetected, because what the design actually builds is known only after elaboration.
I present a Bazel build-integrated flow tool that derives block stimulus from the elaborated design: one cache-gated slang elaboration of the SoC top is inverted into a per-module manifest of the parameter tuples each module is really instantiated with, and each is run at test time through the block's existing testcases, deduplicated against hand-written corners with coverage merged across runs. Deriving configurations inside the build graph rather than committing them means new instantiations are verified on the next regression, with no manual refresh and no staleness. I discuss the load-time/execution-time boundary that shapes such flows and results from a widely instantiated block whose hand-written sweep was missing real configurations.
Block-level verification of parameterised RTL relies on hand-written parameter sets chosen from designer intent, not the assembled design. As the SoC grows, the two drift, and that gap goes undetected, because what the design actually builds is known only after elaboration.
I present a Bazel build-integrated flow tool that derives block stimulus from the elaborated design: one cache-gated slang elaboration of the SoC top is inverted into a per-module manifest of the parameter tuples each module is really instantiated with, and each is run at test time through the block's existing testcases, deduplicated against hand-written corners with coverage merged across runs. Deriving configurations inside the build graph rather than committing them means new instantiations are verified on the next regression, with no manual refresh and no staleness. I discuss the load-time/execution-time boundary that shapes such flows and results from a widely instantiated block whose hand-written sweep was missing real configurations.
, a project that connects ngspice to a VPI-capable HDL simulator. SpiceBind allows an RTL block to be replaced by its SPICE implementation while keeping the existing HDL or cocotb testbench and the familiar waveform and debug flow. This provides a simple way to include transistor-level circuits in an RTL verification environment. SpiceBind: Bringing SPICE into RTL Verification (Tomasz Hemperek)](https://i.ytimg.com/vi/X9tjylQ0Rv4/mqdefault.jpg)









