Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutRoadmapCareersInternshipsFAQContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Paths
  • Glossary
  • Metrics Reference
  • Formal Cheat Sheet
  • Formal Foundations19
  • Properties and SVA16
  • Property Development and Constraints19
  • Proof Engines and Convergence23
  • Formal Applications20
  • Equivalence Checking14
    • Combinational Equivalence and the Miter
    • Sequential Equivalence
    • RTL to Gate: What LEC Assumes
      • What LEC Assumes
      • Key Points and Unmapped State
      • Retiming, Gating and the Limits of LEC
    • ECO and Alternative-Implementation Checks
  • Formal Coverage and Signoff15
  • Methodology and Debug13
  • Interview Prep15
  • Capstone: A Chip-Block Verification Lab24
Loading lesson

←Equivalence Checking
  1. Topics
  2. Formal Verification
  3. Equivalence Checking
  4. RTL to Gate: What LEC Assumes

Part 6 of 10Part 6 of 10/Equivalence CheckingAll levels

RTL to Gate: What LEC Assumes

The gate-level pass rests on one-to-one state, quiet scan, matching constants and the same reset: list them or do not claim it.

  • 3topics
  • 3lessons

The synthesis flow hands over a netlist and a passing comparison, and the signoff treats the RTL proof as proven for silicon. That transfer is sound only under assumptions nobody simulated: every flop matched one-to-one, scan and test disabled, constants identical, reset the same. This topic lists those assumptions, shows the false pass or false fail each one produces, and draws the line where one-to-one comparison stops working.

Lesson

After it you can...

What LEC Assumes

State the four assumptions and the failure each one causes.

Key Points and Unmapped State

Find correspondence by name, structure and function, and classify unmapped points.

Retiming, Gating and the Limits of LEC

Say which transformations need sequential methods, and what a PASS means.

Suggested order: top to bottom. Assumptions first, because everything else is a footnote to them; key points next, because unmapped state is the most common finding; limits last, because it tells you when to stop using the method. The flow view this complements lives at Equivalence Checking.

RTL flops and gate flops are matched one to one, then constants, scan and reset are checked in turn before a pass may be claimed.
The four assumptions behind a gate-level pass: one-to-one state, equal constants, quiet scan, same reset.
Check yourself A gate-level comparison passes with scan enabled on one side. What does the pass prove?

Very little: the compared logic includes test paths the mission mode never exercises, and may exclude mission paths the test logic overrides. Disable scan on both sides and rerun.

If asked what a logic-equivalence pass assumes, list the four from the diagram in order. The four are state correspondence, constants and black boxes, scan, reset. Missing one is what a follow-up question finds.

PreviousNext: What LEC Assumes

Up next

Up nextWhat LEC Assumes

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • Combinational Equivalence and the Miter
  • Sequential Equivalence
  • ECO and Alternative-Implementation Checks