Re:FPGA Interchange format to enable interoperable FPGA tooling
by duskwuff on Saturday February 12, 2022 @08:47PM
(#30318315)
HDLs like VHDL and Verilog are at a different level. If HDLs are like C, the interchange format is more comparable to a .o file.
That being said, EDIF already exists.
Re:FPGA Interchange format to enable interoperable FPGA tooling
by Taniwha on Saturday February 12, 2022 @09:07PM
(#30318424)
we've commonly used verilog (just instantiating gates) to do this - partly because for a period (ie the 90s) we didn't really trust synthesis tools to get it right and always ran gatesim before we taped out just in case.
My crowning glory hack from that era was a perl script that read verilog netlists and lisp placement data between the place and route stages of the P&R tool and did location dependent scan insertion producing a netlist and a the lisp instructions to the P&R tool to fix it up
Re:FPGA Interchange format to enable interoperable FPGA tooling
by Rochus on Saturday February 12, 2022 @09:08PM
(#30318429)
You can pretty well represent low-level netlists in Verilog.
EDIF is big and complex and there are different only partially compatible versions in parallel use.
Re:FPGA Interchange format to enable interoperable FPGA tooling
by mithro on Saturday February 12, 2022 @11:03PM
(#30319104)
On a semi-related note, Google has also been investigating in improving support for SystemVerilog support in open source tooling -> https://opensource.googleblog.com/2021/09/open-source-system...
Re:FPGA Interchange format to enable interoperable FPGA tooling
by ip26 on Saturday February 12, 2022 @11:49PM
(#30319312)
HDL can really be either. I would compare RTL to assembly, and gate netlists to .o files.
Re:FPGA Interchange format to enable interoperable FPGA tooling
by octoberfranklin on Sunday February 13, 2022 @03:06AM
(#30320121)
Xilinx is a software company.
They consider their chips to be the copy-protection dongles for the software.
It's nuts, and it infuriates me, but looking at it this way explains a whole lot of their behavior.
Players like Xilinx have held out their compliers and instead selling them and using lawsuit to prevent people from reverse engineering there IP. This hasn't stopped people or lesser players like lattice from doing this but it's definitely slowed it down. I think open sourcing or releasing the compliers is just kind of forced because what new company would but a complier if they can get one for free (yosys).