FORMAL VERIFICATION COMPANY · BENGALURU, INDIA

Prove your RTL is right
before tape-out.

Formal verification engineers and sign-off for critical digital IP and SoCs, inside your flow, on your tools.

FormForgeIQ Formal verification workflow platform · Contact us to learn more

FORMFORGEIQ


Formal verification workflow platform · Contact us to learn more

Why it matters

Respins don’t start in the lab. They start with bugs nobody tested for.

These are the three problems we hear from verification managers most often, and how TSIQ removes each one.

The problem

Simulation passes, silicon fails

Random tests can run a long time without hitting the one corner case that locks up your chip.

With TSIQ

Every reachable state is checked

We prove your block mathematically, so deadlocks, races and lost data are found before tape-out, not after.

The problem

Formal engineers are hard to hire

Experienced formal talent is scarce, and building a team in-house takes time you don’t have.

With TSIQ

A ready formal team

Planning, proofs, convergence and review, already working together. You add formal capacity without a hiring cycle.

The problem

Green results that prove nothing

Over-constrained assumptions and vacuous proofs give false confidence right up to tape-out.

With TSIQ

Sign-off you can audit

Every assumption validated, every cover reached, and every result reviewed by an engineer who didn’t run it.

Why TeraSilicon IQ

Why teams choose TeraSilicon IQ

01

Formal is our core

Not a side offering. Formal verification is what our methodology, tools and team are built around.

02

Proof, not promises

You get a reviewed sign-off package with every property, assumption and bug, committed to your repository.

03

Start small, see results

Begin with one block. Judge us on what we find before you commit to anything bigger.

04

With you to tape-out

Synthesis, LEC and STA support carries your formal intent through ECOs and timing.

See how

Outcomes

What you walk away with

Every engagement ends with results your managers, reviewers and future teams can use.

  • Bugs found before siliconEvery counterexample traced to a root cause, fixed and re-proven.
  • A sign-off your reviewers trustProof status, coverage, assumptions and residual risk, in one reviewed package.
  • Properties you keepSVA, scripts and run setups stay in your repository as regression checks for every future change.
  • Time back for your DV teamYour engineers focus on the system while we close the blocks that need formal.

The team

A complete formal team, not just extra hands

Every function a formal sign-off needs is covered on your engagement, with one engagement lead answering for all of it.

On every engagement

  • Planning and sign-off criteriaCovered
  • Property developmentCovered
  • Proof runs and debugCovered
  • Hard-proof convergenceCovered
  • Equivalence and ECOsCovered
  • CDC and security proofsCovered
  • Independent reviewCovered

One engagement lead answers for all of it.

Getting started

Getting started is simple

  1. Talk to us

    A short technical call about your block and your risks. No design data needed.

    No design data
  2. Run a pilot

    One block, fixed scope, sign-off criteria agreed up front. You see real results.

    Fixed scope
  3. Scale with confidence

    Expand to more blocks or a full programme once the pilot has proven its value.

    Your pace

Sign-off for a block

We take a critical block from spec to a reviewed formal sign-off package.

Plan a block

Formal engineers in your team

Our engineers join your team onsite or remote, with TSIQ oversight behind them.

Request profiles

Partner capacity

Formal capacity for design companies delivering their own customer programmes.

Explore partnerships

Explore

See how we think before you call us

Formal verification

See what formal catches

Problems simulation passes and formal catches, and how we solve each one.

Open
By design area

Is your block right for formal?

See what formal proves in your design area and the bugs it typically catches.

Open
Sample deliverable

Open a sign-off package

See exactly what you receive at the end.

Open
For engineers

A first formal check

A FIFO reference model and data-integrity assertion in SVA.

Open

FormForgeIQ

FORMFORGEIQ

The workflow behind our sign-off

Our own formal verification workflow platform, built to track properties, proof status, assumptions and evidence across every run.

  • Every property trackedStatus, depth and review state in one place.
  • Assumptions under controlA living register, so over-constraint never hides a bug.
  • Evidence, ready to reviewSign-off packages built from real run data.
A register of properties, assumptions and covers, each with its statusPROPERTY REGISTERp_fifo_orderPROVENp_no_overflowPROVENa_valid_holdREVIEWEDc_full_reachCOVEREDp_credit_okPROVEN

HOW WE WORK WITH YOU

Choose the right way to engage our formal team

Start with a pilot block, then choose the level of support that fits your programme. All work is delivered from Bengaluru, under NDA, and reviewed by your senior engineers or your partner’s.

Formal Verification Sign-Off

Take a critical block from specification to a reviewable sign-off package.

Formal Verification, Delivered From Bengaluru

Our engineers work on your block, on your tools, under NDA, from Bengaluru. You get proof results and a sign-off package — not people to manage onsite.

Engineering Partnerships

Formal capacity for engineering companies and formal partners: overflow support or a defined work package, under your process.

Design areas

Where formal verification applies

Processor / CPU control

decode, pipeline, privilege

Cache / memory

coherence, DMA, ECC

Interconnect / NoC

AXI, APB, CHI, deadlock

Hardware security

information flow, secure boot

Compute / datapath

arithmetic, rounding, latency

Power, clock, reset

FSM, isolation, reset order

CDC / RDC

async FIFO, Gray code, handshake

Equivalence / integration

RTL ECO, connectivity, CSR

What formal checks in each area →

What a pilot hands over

A sign-off package you can review line by line

Every pilot ends with the same set of artefacts, so your senior engineers can check the work without rerunning it. Below is an example of the layout. The names and results are illustrative, not client data.

signoff_report · example block

Property results

PropertyKindResultNote
a_fifo_no_overflowassertProvenFull proof
a_req_eventually_gntassertBoundedDepth agreed in the verification plan
c_fifo_full_reachablecoverReachedWitness trace attached
m_valid_stable_until_readyassumeReviewedSigned off with the designer
a_rd_ptr_wrapassertCEX, fixedRTL issue found, fix re-proven

Sign-off conditions

  • Every assertion proven or bounded
  • Every cover reached
  • Every assumption reviewed
  • Every counterexample closed
  • Results reproducible
  • Peer-reviewed before delivery
Example layout. Not client data.
  1. 01

    Verification plan

    What is checked, what is out of scope, proof-depth targets and sign-off criteria, agreed before the first run.

  2. 02

    Property and assumption register

    Every assertion, cover and assumption with its intent, owner and review status.

  3. 03

    Counterexample triage log

    Each failure traced to an RTL issue, a missing assumption or a spec question, with how it was closed.

  4. 04

    Sign-off report and run scripts

    Results against the six conditions, plus scripts so your team can reproduce every proof on your tools.

Discuss a pilot block →

Engineering reference work

An evidence-based engineering portfolio

We are preparing internal engineering reference projects. They are internal engineering work, not customer projects, and none is published until its results have been reviewed.

Each published reference project will include:

  • Reference design or block
  • Exact RTL/version used
  • Verification objective
  • Assumptions and verification plan
  • Properties and proof results
  • Bugs identified, where applicable
  • Coverage and limitations
  • Technical review status

Engineering reference projects