Paths to a chip

Process migration.

An existing design moved to a new process node or a new foundry, for lower cost and power, more capacity or a second source. The function stays; the libraries, memories, IP, timing and test are rebuilt for the target process.

For
Companies with a chip in design or in production that needs a new node or a new foundry
You provide
RTL or a netlist, constraints, the present sign-off results, and the IP and memory lists
You receive
A migration assessment first, then signed-off GDSII on the target process
Process experience
Six process nodes, from 28 nm to 6 nm

What moves, and what is rebuilt

The function stays; the implementation is redone.

  1. Function

    The RTL and its verification carry over, and behaviour is proven equivalent after the move.

  2. Libraries

    Standard cells of the target process, re-characterised where the operating voltage calls for it.

  3. Memories and IP

    Each memory, PLL, I/O and third-party block is replaced by its equivalent on the target process, or redesigned where none exists.

  4. Timing and power

    Synthesis, placement and clocking are run again, and timing and power are closed across the new corners.

  5. Custom blocks

    Full-custom cells and hand-placed blocks are redrawn for the new design rules.

  6. Test and package

    Test programs are re-validated, and the package and pin-out are kept where the product needs a drop-in part.

Questions about process migration

Why migrate a design that works?

For a smaller die and lower power on a finer node, for capacity or a second source at another foundry, or because the present process is being retired.

Is a migration always a redesign?

No. It depends on how close the two processes are, and some are made for it: TSMC states that its N6 process has design rules fully compatible with N7 and allows direct migration of N7 designs (TSMC press release, 16 April 2019).

Can the new chip replace the old one on the same board?

It can, where the package and pin-out are kept and the electrical behaviour is matched. The assessment sets out what has to match.

How do you know the migrated design behaves the same?

Equivalence checking against the original netlist, the original verification suite run again, and timing and power signed off on the target process.

Which processes do you work on?

We are a TSMC direct account, and our design work spans six process nodes, from 28 nm to 6 nm.

A design that needs a new process?

Tell us the present process, the target and why you are moving.

  1. Fill in the project form
  2. We reply by email within a few working days
  3. Onboarding: NDA, design review and a staged plan

The form is the fastest way to reach us. A person reads every request.