Paths to a chip

FPGA to ASIC conversion.

Your product works on an FPGA, and volume, power or size now ask for more. We turn the design into an ASIC: the logic stays yours, and what the FPGA device supplied ready-made, its memories, clocking, I/O and configuration, is rebuilt for silicon.

For
Companies shipping a product on an FPGA, or holding an FPGA prototype they want to ship in volume
You provide
The FPGA project: RTL, constraints, the device it runs on, and your volume and cost targets
You receive
An ASIC designed, verified and taped out for your product
First step
An ASIC feasibility study or an RTL assessment

Why convert

When an FPGA has done its job.

  1. Unit cost

    At volume, an ASIC costs less per part than the FPGA, once the one-off cost is carried.

  2. Power and size

    An ASIC holds only your logic, so it draws less power and fits a smaller package.

  3. Supply

    Your own chip is ordered on your schedule, and does not go end-of-life with a device family.

  4. Performance

    Paths that the FPGA fabric limits can run faster on standard cells.

What changes

What an ASIC asks of an FPGA design.

  1. Memories

    Block RAM becomes SRAM macros, with built-in self-test.

  2. Clocks and resets

    The FPGA's clock managers become PLLs and a clock tree; registers that relied on power-up values get an explicit reset.

  3. Arithmetic blocks and vendor IP

    DSP blocks, transceivers and vendor cores are replaced by ASIC IP, or redesigned.

  4. I/O and package

    The pad ring, I/O standards and package are chosen for the product, and kept pin-compatible with the FPGA where the board needs it.

  5. Test

    Scan, memory BIST and ATPG are added, so every part can be screened in production.

  6. Verification

    The FPGA proved the function in the lab; the ASIC is verified in simulation before the masks, and the FPGA stays on as the prototype.

How it runs

Six steps, from assessment to delivery.

  1. Feasibility and cost

    Whether the conversion pays at your volumes, and on which process.

  2. RTL assessment

    Your FPGA RTL, read for what an ASIC needs.

  3. Conversion and verification

    The parts tied to the FPGA device are replaced, and the design is verified against the original.

  4. Physical design and sign-off

    Place and route, then timing, power and physical sign-off.

  5. Tape-out

    A multi-project wafer to prove the design, or a full mask set.

  6. Production

    Wafers, packaging, test and delivery.

Questions about FPGA to ASIC conversion

When does FPGA to ASIC conversion pay off?

When the saving per part, multiplied by the parts you will ship over the product's life, exceeds the one-off cost of the ASIC; or when the FPGA cannot meet the power, size or supply the product needs. A feasibility study works this out for your product.

Can the ASIC replace the FPGA on the same board?

It can, where the package and the I/O standards allow. The assessment confirms it early.

Do we have to rewrite our RTL?

Most of it carries over. The parts tied to the FPGA device, its memories, clocking, vendor IP and I/O, are replaced, and the rest is checked for constructs that behave differently on an ASIC.

Is the FPGA still useful afterwards?

Yes, as the prototype: a change is tried on the FPGA before it goes into the ASIC.

Who owns the converted design?

Ownership of the design and its data is set in the contract for each project.

Shipping on an FPGA?

Tell us the device, your volumes and what you need to improve.

  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.