Skip to content
hw.dev
hw.dev/signal/sky130-dsp-fft-regenerated-rtl-ci-2026
Signalsky130-dsp-fft

A Fresh Regeneration Must Match Every Committed RTL Byte

sky130-dsp-fft makes continuous integration prove that committed generated hardware still matches a fresh run of its generator byte for byte.

Thesis connection

Generated chip logic becomes reviewable when every build can prove which parameters and generator produced it.

#eda#testing#verification#software
Read Original

sky130-dsp-fft now makes continuous integration (CI) regenerate its register-transfer level (RTL) hardware description and compare every byte with the version in the repository. The project generates a 256-point fast Fourier transform, a circuit for converting sampled data into frequency components. Before this change, its documented generator tests weren't running in CI, so a hand edit to generated output could pass unnoticed.

The new check runs the Python generator suite after the existing numerical tests. Its negative control copies the RTL tree, appends one byte to fft256.v, and requires the exact comparison to fail for that file. That second test matters: it proves the freshness check can catch drift instead of merely proving that the generator runs.

Generated hardware is only reproducible when the repository can reject output that didn't come from its pinned generator and parameter file. Any team committing generated RTL should plant the same one-byte mutation in a copy during CI; if the build stays green, the provenance claim is only documentation.