-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Verilator] Split top_*_verilator into testbench and chip-level module #6103
Comments
@msfschaffner any idea what became of this? |
the status is still the same as the last update. |
@tjaychen do we want to take another stab at this? The biggest issue here is probably how the verilator TB currently handles tristate drivers. It pulls out the in/out/oe signals explicitly into the DPI, likely due to limitations in Verilator's tristate modeling. So this may cause issues with the padring, and may require to breakout more signals at the chip boundary than just the pad signals themselves. |
i was wondering about this.. it's not super clear to me how the verilator stuff is going to evolve for separate tops. |
We may want to take another look at Verilator's capabilities in more recent versions as well. Antmicro has been bringing a lot of enhancements. :) |
Ok then P3 sounds right then. I'll unassign us for now, since we are not actively working on it. |
We potentially want to align the verilator TB for PROD to ease SW development. |
Split out from #5221.
The text was updated successfully, but these errors were encountered: