Novomorphic

From RTL to a sign-off pack your customer accepts

Design, verification, DFT and implementation, with evidence that survives an audit.

What you get
  • UVM verification plan and coverage closure
  • DFT and ATPG
  • Timing-closed netlist and sign-off pack
Applied in
GRID-5G, SENTINEL-AI
Sectors
Aerospace & Defence, Energy & Critical Infrastructure, Telecoms & Open RAN
First step
Architecture workshopOne to two days. Written opinion within a week.

When to bring us in

The situations this solves

  • You have RTL and no verification story a safety or security assessor will accept.

  • Timing will not close and the fixes keep breaking something else.

  • You need DFT designed in rather than discovered at test.

  • Your team can do the design but not the sign-off, or can do the sign-off but has no capacity.

  • The digital block is one part of a mixed-signal system and you would rather one team owned the whole thing.

What changes

Closure becomes a schedule, not a hope

Coverage closure becomes a schedule you can plan against rather than a curve that flattens near the deadline.

Test coverage and fault grading are known before tape-out. Timing closure stops being an iterative surprise, because the constraints were written at architecture.

The verification artefacts, meaning the plan, coverage model, results and traceability, exist as a pack, because that is what a regulated customer asks for and it is expensive to reconstruct afterwards.

Scope

What is in scope

  • Micro-architecture and RTL design
  • Functional verification: UVM testbench architecture, constrained-random and directed stimulus, functional and code coverage closure, assertion-based verification
  • Formal property verification where it earns its place
  • Low-power design and UPF-based power intent
  • Design for test: scan insertion, ATPG, compression, memory BIST, boundary scan
  • Synthesis, static timing analysis, constraint development and timing closure
  • Place and route, physical verification and sign-off to GDSII
  • Bring-up support and silicon debug

Not included

We do not own your foundry relationship or PDK licensing, and we do not publish process-specific detail. Where a block is better bought than built, we will tell you which IP vendor to talk to.

INTERACTIVE · CUSTOM SILICON

From one requirement to tape-out

Play the flow and watch the chip take shape.

EXAMPLE EDGE AI CHIP
COMPUTE · DIGITAL

AI accelerator

Built around the model, so it fits the power budget.

29% of the die
OWNED BYSecure edge AI

You get: Bring-up plan

Example architecture, for illustration.

How we work

Verification is planned with the specification, not after the RTL

  1. Specification and verification plan together

    The verification plan is written alongside the specification, not after the RTL. An untestable requirement is caught here, when it costs a conversation.

  2. RTL and testbench in parallel

    Coverage model agreed at the start so closure is measurable from week one.

  3. DFT and power intent inserted early

    Not retrofitted around a design that did not expect them.

  4. Timing closure and sign-off

    Constraints reviewed against the architecture’s original budgets, not invented at implementation.

  5. Handover and bring-up

    Sign-off pack, traceability and silicon debug support.

5 pages, PDF

Digital ASIC design, verification and DFT: capability brief

RTL to GDSII with the verification evidence to back it. A short brief covering when to bring us in, what is in scope and what is not, how the work runs, and the questions buyers ask first.

What’s inside

  • When to bring us in, and what you have at the end
  • What is in scope, and what is not
  • How the work runs, step by step
  • Straight answers to the questions buyers ask first

Read next: Mixed-signal and RF ASIC design: capability brief

In fifty seconds

From specification to sign-off

Digital ASIC, in 50 seconds.

FAQ

Questions about Digital ASIC

Which toolchain do you work in?

We are a Cadence Design Network Partner and design on the industry-standard flow. We work in the customer’s environment where that is a requirement.

Can you take over an in-flight design?

Yes. Expect a short assessment phase first. Inheriting undocumented constraints without reviewing them is how a second respin happens.

Do you provide the verification evidence pack?

Yes: plan, coverage model, results, traceability and a review record. Ask early if there is a specific standard it must satisfy.

Do you work to functional safety or security standards?

We design to them where the programme requires it, and we are explicit about the boundary between design evidence and formal certification.

Who owns the IP?

Agreed in the contract before work starts. Foreground IP created for you is normally yours; our background IP stays ours and is licensed for use.

Talk to an engineer about Digital ASIC

An engineer reviews every enquiry. We will come back with a technical view, not a brochure.

Everything you send is treated as confidential. We can sign an NDA before any technical detail is exchanged.

What happens next

1

An engineer reads it

Not a form-handler. Whoever owns the relevant discipline.

2

We come back with a technical view

Including if we think you do not need us.

3

If it looks like a fit, a short technical call

Then, if it is useful, a scoped workshop, feasibility study or evaluation.