bb-collect-coverage

Verilator coverage is computed by aggregating line, branch, toggle, and functional metrics from coverage.dat and simulation logs, producing unified coverage percentages and a coverage.json file.

Uncovered bins are identified by aggregating metrics from coverage.dat and sim logs to enumerate bins with zero hits, guiding your test expansion efforts during Verilator regression runs.

Yes, you can enforce target thresholds for functional and code coverage. The process reads coverage.dat and sim logs to trigger sign-off only when the specified coverage targets are met.

The best way to generate a unified coverage report is to consolidate simulation logs and coverage.dat into design-wide outputs like coverage.json and test_report.json aligned to the project schema.

No, bb-collect-coverage requires no external dependencies to parse coverage data. It directly reads the Verilator coverage.dat file and simulation logs to output the coverage metrics.