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
  • The NanoSoC Tour
  • Reading Path
  • SoC Glossary10
  • SoC Metrics Reference
  • SoC Cheatsheet
  • What SoC Integration Is12
  • Architecture and Budgets21
  • Memory Maps and Address Decode26
  • Interconnect and Bus Fabrics26
  • Clock and Reset Architecture24
  • Power Architecture21
  • Interrupts, DMA and Peripherals15
  • Memories, Boot and Security21
  • IP Integration and Handoff21
  • Top-Level Verification and Bring-up21
    • SoC Verification Strategy
    • Integration and Connectivity Tests
    • Firmware Co-Simulation
    • Performance Verification
    • Gate-Level and Power-Aware Simulation
      • What Gate-Level Simulation Finds
      • X-Propagation, Reset Order and Timing
      • Power-Aware Simulation and Isolation Checks
    • Emulation and FPGA Prototyping
    • Bring-Up Readiness
  • Package, Pads and I/O18
  • Chip Signoff and Tapeout18
  • SoC Interview Prep16
  • Capstone: Integrate NanoSoC14
Loading lesson

←Top-Level Verification and Bring-up
  1. Topics
  2. SoC Design
  3. Top-Level Verification and Bring-up
  4. Gate-Level and Power-Aware Simulation

Part 10 of 14Part 10 of 14/Top-Level Verification and Bring-upAll levels

Gate-Level and Power-Aware Simulation

What each finds beyond RTL: netlist fidelity, X-propagation, isolation and retention, reset-order bugs, and their cost.

  • 3topics
  • 3lessons

RTL simulation proves the design as written; the chip is built from the netlist as synthesised, placed and powered. Gate-level simulation closes the first gap — what the tools changed — and power-aware simulation closes the second — what the power intent adds. On NanoSoC these two runs find the failure classes RTL cannot show: an ECO the equivalence check missed, an X the RTL optimised away, two missing isolation clamps, a restore that runs before power is stable. This topic teaches both lenses, what each costs, and when each runs.

Lesson

After it you can...

What Gate-Level Simulation Finds

Say what GLS adds over RTL and run it after every netlist change.

X-Propagation, Reset Order and Timing

Read an X to its source and prove the reset order in the netlist.

Power-Aware Simulation and Isolation Checks

Check isolation, retention and sequencing with the power intent active.

Suggested order: top to bottom. Gate-level first, because it replays the known-good RTL tests on the netlist; then the X and reset analysis, which is where most GLS debug time goes; then power-aware, which adds the intent dimension. For the debug-side view see the gate-level lesson linked below; this topic is the integrator's when-and-what. The ten planted bugs it refers to are listed in the NanoSoC tour.

Check yourself Why does GLS replay the RTL suite instead of using its own tests?

Its job is fidelity, not function: same stimulus on both models, and any divergence is a netlist or timing fact. New tests would confound function bugs with fidelity bugs.

Expect to justify GLS cost: a large multiple of RTL for bugs only a netlist can show. Name three: reset-tree skew, X optimism hiding a bug, and an unverified ECO.

PreviousNext: What Gate-Level Simulation Finds

Up next

Up nextWhat Gate-Level Simulation Finds

Sign in to save progress

Practice this lessonPrevious lessonReport an error

See also

  • SoC Verification Strategy
  • Integration and Connectivity Tests
  • Firmware Co-Simulation