Open stdefeber opened 2 weeks ago
One step futher.
parameters DW, MSG_LEN and MSG_STR are indeed no part of vlog_tb_utils.
Running the example with:
fusesoc run axis_send_packet --vcd
still gives compile errors:
poetry run fusesoc run axis_send_packet --vcd
However:
poetry run fusesoc run axis_send_packet --MSG_LEN=11 --MSG_STR=hello_world
Gives a pass. However I got no VCD file. Which is obvious since this is taken care of in vlog_tb_utils.
This was caused by a change in Icarus Verilog where a previous warning now is an error. I just filed https://github.com/steveicarus/iverilog/issues/1137 in the hope that this can be downgraded to a warning again. We can add a workaround in the meantime, but they will be a bit more clunky compared to the current solution.
Long term there should be syntax in FuseSoC to select which parameters that goes to which toplevel, but there are other things that are of higher priority to fix. A quick workaround is to change the toplevel line from toplevel : [axis_send_packet, vlog_tb_utils]
to toplevel : axis_send_packet
but that will also not give you a VCD.
I will come up with a better temporary workaround soon.
I pushed some fixes now. Please let me know if those solve your issues.
The fix works.
Isn't it possible to have the vlog_tb_utils as an include file ?
As wannabe fusesoc user I wanted to start of with the given FuseSoc+CoCoTb example. However I got compile errors.
Environment:
Installed packages via poetry:
I found that the parameters are defined "axis_send_packet.v"
What am I missing/doing wrong ?
br,
ST