I can totally recognize that, but with a third item 3) Vendor uses encrypted model so need to use commercial sim (e.g. ModelSim, XSim) Of course, with FuseSoC it's dead easy to try different simulators for different needs :)
Many of my FPGA projects follow a standard two-act dramatic structure: 1) Behavioral sim: could use verilator but iverilog is fast enough. 2) Sim using vendor models: iverilog takes forever and vendor models don't work with verilator.
-
-
-
This Tweet is unavailable.
- Show replies
New conversation -
-
-
Ditto. And how did we end up where we're coding a behavioural sim in a badly-designed weak language like System Verilog instead of in a proper programming language like Python?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
That's only true for short simulations. I can testify to 20-30x speedups for certain long-running simulations with Verilator. There's an attempt to Verilator proof some vendor building blockshttps://github.com/dirjud/Nitro-Parts-lib-Xilinx …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.