Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
f4pga-arch-defs
FOSS architecture definitions of FPGA hardware useful for doing PnR device generation.
Soon: there are 15 different formats for passing netlists around.
I have very little hope that any netlist format that comes from Yosys. Not only has it changed a couple times in the last years, but the latest iteration is some JSON-based monstrosity that has to be by far the most inconvenient netlist format ever created (see https://github.com/nturley/netlistsvg/blob/master/test/digit... ) .
Or BLIF or EBLIF (already used by the verilog-to-routing flow). But no, let's invent yet another netlist format.
The fact that all of these existing formats are all named "xxx logic interchange format" should give you an idea what will happen to this new "interchange format".
From what I gather ( https://github.com/SymbiFlow/python-fpga-interchange/blob/ma... ) , the new format is basically the existing Yosys/nextpnr JSON format except dumped as a Cap'n Proto binary file.
I am absolutely not impressed.
I guess the meat here is on the universal device resources format, but this is not cool anyway.
Did any project other than Chisel make use of FIRRTL? https://github.com/chipsalliance/firrtl
Related posts
- An addressable little explored language gap: HDL - Hardware Description Languages, any language used for electronic circuit design, description, and specs
- 1800-2023 – IEEE Standard for SystemVerilog
- FuryGpu – Custom PCIe FPGA GPU
- Barcelona Supercomputing Center presents Sargantana: new open-source RISC-V chip
- SERV – The SErial RISC-V CPU