../

Periscope Writing Ideas

Introduction

Comprehensive formal verification has exacerbated strenuosity due to the ballooning size and increasingly complex modern hardware designs. This combined with the sheer influx of new (possibly bug-ridden) designs created by LLM accelerated development clamors for robust pre-silicon verification.

Assertions are hard

The division of labor between designers and verification engineers as to who writes assertions leaves us stuck between Scylla and Charybdis.

Tasking the designers to write assertions for their parts, trades in ambiguity for incompleteness. wangAutomaticGenerationAssertions1998 bouleGeneratingHardwareAssertion2008

Leaving it mostly to verification engineers, following Bergeron2000, asks of them to completely understand the design which is bound to not scale. wangAutomaticGenerationAssertions1998 jenihhinReusabilityVerificationAssertions2008 trippelSpecificationFormalVerification2025

Furthermore, the possible lack to documentation makes this a game of charades where VE is stuck trying to guess the design intent while also missing intents that they don’t understand. hangalIODINEToolAutomatically2005 feyRobustnessUsabilityModern2008

Combining LLMs into static

Missing piece

For larger hardware designs, such as a microprocessor, there exists an asymmetry between simulation and emulation. Furthermore, to err on the side of caution, the formal environment starts off severely under constrained.  When we over-constrain, we are susceptible to false signoffs which are a ticking timebomb in the post-silicon world. This means that we require two crucial feedback mechanisms - the Simulation-Emulation gap and the RV-FV gap.  We believe these two critical pieces are missing in contemporary open loop works such as HARM and Goldmine that our framework fixes.