RTL verification for semiconductor and RISC-V teams
Know what failed. Know what to do next.
We investigate RTL failures, close defined coverage gaps, and build checks for your design. Start with one problem and an agreed result.
See real coverage holes and bug reports on open source RISC-V cores, each taken to a proof or a test
Where we help
Start with what is blocking your team.
Each item in the list is a problem we solve. Open one to see how we work on it and what you receive.
RISC-V
Coverage
Correctness
Data across clocks
RISC-V verification
Turn an architectural requirement or failure report into checks your team can inspect and rerun.
- 01
Define the rule
Identify the required behaviour and its configuration or software assumptions.
- 02
Exercise the RTL
Use tests or properties to expose a violating sequence.
- 03
Hand over the evidence
Record the result, proposed correction, and remaining limits.
What you receive
- A test plan tied to the agreed architectural requirement.
- Reproduction scripts, run settings, and evidence for observed failures.
- Checks of the proposed correction and any remaining unknowns.
Real work you can check
A waived condition that could still happen.
In an open source RISC-V core, two conditions on one controller line had been waived with no proof or test behind the waiver. We proved one can never happen. The other can, so it must not be waived, and we wrote a test that reaches it.
A public issue on an open source core. The full report and the issue are linked from the case.
- 01
Find out why
Read the design to see when each condition could arise, starting from what the original issue said.
- 02
Prove or reach
Prove the impossible case with formal verification, which checks every reachable state. Use a formal search to find a real path to the other.
- 03
Leave a test
Write a test that reaches the possible case, so it stays in coverage instead of hiding behind a waiver.
What comes back to you
An answer your team can work with.
A sample investigation handover.
The finding
What the checks established, any identified cause, and what remains open.
The evidence
The agreed tests, properties, logs, and traces behind the conclusion.
The handover
Run instructions, assumptions, and limits so your team can continue the work.
Working together
Start with one defined problem.
Bring one failing test, unexplained result, or coverage gap. We review feasibility and agree what to investigate before work begins. A good first piece of work is one coverage hole or one bug: you get a report, the proof or test, and the files to rerun it yourself.
- 01
Describe the blocker
Describe the design and issue using only non confidential context.
- 02
Agree the work
Inputs, deliverables, access, and completion criteria in writing.
- 03
Review the result
Walk through the findings and rerun the agreed checks in your environment.
Bring us the verification problem that is holding up your team.
Describe the problem in a few lines. An engineer replies, and we agree the scope together.
Discuss a verification problem