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
- Leaving them up to the designer can lead to incomplete specifications wangAutomaticGenerationAssertions1998 bouleGeneratingHardwareAssertion2008
- On the other extreme, tasking a verification engineer to come up with them requires them to fully understand the design (scaling issue) wangAutomaticGenerationAssertions1998jenihhinReusabilityVerificationAssertions2008 trippelSpecificationFormalVerification2025 or can cause a guessing game between the VE and Designer in the cases of non-existent documentation hangalIODINEToolAutomatically2005feyRobustnessUsabilityModern2008
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