FPGA and component obsolescence
We move designs off end-of-life FPGAs, and replace processors and chips that are no longer made.
FPGA migration
Older FPGA families go end-of-life while the products they sit in keep shipping. Migration means re-targeting the design to a current device, replacing vendor IP that no longer exists, closing timing again, and proving the new build behaves like the old one.
Legacy chip replacement
When the obsolete part is a processor, DSP or interface chip, we rebuild it on FPGA so the existing software runs unchanged. See legacy processor and chip replacement. Part families we replace: Motorola 68000 family (68000–68040) , Embedded PowerPC (603e, 750, MPC5xx, PowerQUICC) , Embedded x86 (80186, 80386EX, 80486) , 8051 / 80C51 and derivatives , Zilog Z80 , MIL-STD-1750A processors , TI TMS320C3x / C4x DSPs , Analog Devices ADSP-21xx and SHARC (2106x) DSPs , MIL-STD-1553 and ARINC 429 controllers .
Frequently asked questions
Which FPGA families do you migrate from?
Older AMD (Xilinx) and Altera generations, such as Virtex-4/5/6, Spartan-3/6 and older Stratix and Cyclone families, to current devices.
What if the original source code is lost?
We can work from the netlist, or re-implement from the specification and verify against the original hardware.
How do you prove the new design is equivalent?
By running the old and new designs against the same tests and comparing outputs, in simulation and on hardware.
Related
Discuss your project
Share the target, interfaces, and timeline. We’ll tell you what we’d take on first.