Example design
Out-of-order CPU
Target property
An instruction must not commit before all older instructions have committed.
founders@chipster.aiFormal verification that learns from every run
Chipster reads a spec and RTL, writes SystemVerilog assertions, and checks them with a formal tool. Assertions that fail stay in the record. Simulation explains why, and that lesson is available on the next design. The engineer reviews what ships.
How it works
Chipster does not ask a model for a single assertion and stop. It searches, proves what it can, keeps the counterexamples, and uses them the next time.
Feed Chipster with Spec and the RTL with extra context for grounding.
Chipster will generate requirements for every signal using a Knowledge Graph. Accept what requirements you want assertions for.
Chipster will start its MCTS algorithm for assertion generation using your EDA formal backend. It will keep the best assertions.
Dropped assertions are replayed in simulation to extract useful insights. These insights make future assertion generation better, prevent repeated mistakes, and surface insights to the engineer.
Start each new design with knowledge from previous runs, enabling faster sign-off and higher coverage.
Example Design
An out-of-order CPU. The property: an instruction must not commit before every older instruction has committed.
Example design
Target property
An instruction must not commit before all older instructions have committed.
1 Generate
assert property (
commit_valid |->
rob_head_idx ==
commit_idx
);Fails, with a counterexample
2 Refine
assert property (
commit_valid |->
!commit_older_pending
);Passes. A stronger assertion
3 Select
4 Learn
Continual learning. The stored lesson comes back into the next generation.
Early results
Chipster is in early access.