Intel® Quartus® Prime lite edition, standard edition, and pro edition software Intel® Quartus® Prime Design Software support Every 12 months you must regenerate your license file in the Self-Service Licensing Center to renew your license for the specific ModelSim*-Intel® FPGA edition software version that you purchased. The ModelSim*-Intel® FPGA edition software license expires 12 months after the date of purchase. Note: The ModelSim*-Intel® FPGA edition software requires a valid license. Then if you can run most of your simulations with one of the free simulators, great, you can run them in parallel to get the quickest simulation times.$1,995 includes software updates for one year I know it's not always possible, but where you can, write code and simulation scripts in a way where you can easily swap simulators. And as a result of simulating in parallel total simulation time comes right down by virtue of loading up the PC with multiple threads/simulations, as opposed to loading up the PC with just the one thread, which is what you get with one simulation for Modelsim, XSim, GHDL and iverilog (at least in my experience). Of course the free GHDL and iverilog will allow you as many simulations as you like. Last time I checked the paid for XSim license I think one license allowed you as many simulations as you like on one machine, but that was a while ago now and I might be mis-remembering and out-of-date. Same with the Xilinx XSim free simulator. At home when I use the free Intel Modelsim, that allows multiple simulations at the same time. In work where I've used paid for Modelsim, each Modesim simulation has always used one license.
I don't really have a large regression I want to run yet, I just want fast debugging, so I think I'll be looking for more single-thread performance in my next machine.ĭon't forget you'll need lots and lots of (ECC) RAM for lots of parallel runs - think 2-4GB minimum _per thread_ but more is better, especially if you can stuff all your memory channels and boost bandwidth.
Vivado simulation processes also seem to be single threaded, which is a bit frustrating. I currently have a 16c/32 thread EPYC that I use for Vivado but it only boosts to 2.7GHz (all core) and so while it flys for multiple synth-runs at the start of a build, it bogs down in the P&R which doesn't use many threads.
Sounds like an interesting setup, I've been thinking of building something similar.
0 kommentar(er)
