toggle coverage

Concept

Toggle coverage is a hardware verification proxy metric that records whether a signal switches from 0 to 1 and from 1 to 0 during test execution. In the Logic Fuzzer work, it is used to show that fuzzing can create additional RTL activity, but the authors caution that toggle coverage and similar code-coverage metrics are not full indicators of verification completeness.

First seen 5/27/2026

Last seen 6/6/2026

Evidence 4 chunks

Wiki v1

WIKI

Definition

Toggle coverage is a hardware verification coverage metric in which a signal is considered toggled if its value switches from 0 → 1 and from 1 → 0 at least once while executing a test. The cited Logic Fuzzer paper describes it as a proxy metric used in both industry and academia to gain confidence about the correctness of a design-under-test.

Use in processor verification

READ FULL ARTICLE →

NEIGHBORHOOD

No graph connections found for this entity yet. It may appear in future ingestion runs.

explore full graph →

RELATIONSHIPS

3 connections

congestor ← uses 90% 1e

Toggle coverage is used to measure the effect of congestors on signal activation.

Logic Fuzzer ← uses 90% 1e

Toggle coverage is used as a proxy metric to demonstrate the effectiveness of Logic Fuzzer.

Deep Reinforcement Learning for Test Generation ← implements 95% 1e

The deep RL framework maximizes toggle coverage.

LINKED ENTITIES

1 links

Logic Fuzzer USES Extracted graph relationship

CITATIONS

7 sources

7 citations — click to expand

[1] Toggle coverage treats a signal as toggled if it switches from 0 to 1 and from 1 to 0 at least once during test execution. [PDF] Effective Processor Verification with Logic Fuzzer Enhanced Co ...

[2] Toggle coverage is described as a proxy metric used in industry and academia to gain confidence in the correctness of a design-under-test. [PDF] Effective Processor Verification with Logic Fuzzer Enhanced Co ...

[3] Logic Fuzzer used toggle coverage to observe additional RTL activity after inserting fuzzing logic and rerunning tests. [PDF] Effective Processor Verification with Logic Fuzzer Enhanced Co ...

[4] In the BOOM example, inserting a congestor at the Reorder Buffer ready signal caused 12 additional frontend signals, 40 core signals, and 32 load-store-unit signals to toggle. [PDF] Effective Processor Verification with Logic Fuzzer Enhanced Co ...

[5] The Logic Fuzzer paper reports that Logic Fuzzer increased toggle coverage by about 1% on average across verification binaries. [PDF] Effective Processor Verification with Logic Fuzzer Enhanced Co ...

[6] The Logic Fuzzer authors caution that toggle coverage and similar code-coverage metrics are proxy metrics, not full indicators that a system is verified. [PDF] Effective Processor Verification with Logic Fuzzer Enhanced Co ...

[7] Among the bugs found by Logic Fuzzer, only bug B12 directly correlated with toggle coverage; three others did not correlate with toggle coverage and were detected through randomized events. [PDF] Effective Processor Verification with Logic Fuzzer Enhanced Co ...