pyverilator
pyverilator copied to clipboard
csail-csg
Python wrapper for verilator model
* flushCall is depreciated and replaced with runFlushCallbacks
I have a program (from https://github.com/namin/bluespec-sandbox) that works with verilator 4.200 but not verilator 4.218. The error is ``` clang++ -I. -MMD -I/usr/local/Cellar/verilator/4.218/share/verilator/include -I/usr/local/Cellar/verilator/4.218/share/verilator/include/vltstd -DVM_COVERAGE=0 -DVM_SC=0 -DVM_TRACE=1 -DVM_TRACE_FST=0 -faligned-new -fbracket-depth=4096...
Why does PyVerilator explicitly check for the .v extension on files? Is there a good reason for this? here is the line: https://github.com/csail-csg/pyverilator/blob/master/pyverilator/pyverilator.py#L409 what if you call your source files...
I am trying to use pyverilog with the register files generated with peakRDL-verilog (https://github.com/hughjackson/PeakRDL-verilog) and I am getting the following error. g++ -I. -MMD -I/usr/local/share/verilator/include -I/usr/local/share/verilator/include/vltstd -DVM_COVERAGE=0 -DVM_SC=0 -DVM_TRACE=1 -faligned-new...
I am trying to use PyVerilator 0.7.0 inside a Docker container and I am getting the following error: ``` error: expected initializer before ‘VL_MT_UNSAFE’ void vl_finish (const char* filename, int...
Recently discovered this library and started integrating into my workflow and I've absolutely loved it, but noticed a few features that were lacking and added them in: 1. SystemVerilog support...
Currently it doesnt seem like PyVerilator supports providing explicit lists of Verilog files to pass down to Verilator, or setting the top module explicitly. Verilator will only find the files...
pyverilator finds internal signals by parsing `VL_SIG*` lines in an `.h` file generated by verilator. The most recent version of verilator looks like it doesn't use the `VL_SIG*` macros anymore....
The test `test_pyverilator_finish_2_same_files` (https://github.com/csail-csg/pyverilator/blob/master/pyverilator/tests/test_pyverilator.py#L633-L692) fails because sim_1 and sim_2 both load the same shared object and the verilator `gotFinish` uses a global variable to track if the simulator has finished....