You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We were wondering if it would be possible to support a flag in firtool that uniquifies the modules under the Dut and Harness. When running timing annotated simulations, after the Dut is synthesized the modules that are common to the Dut and Harness will collide and cause simulation to fail.
Is there some specific requirements for this? I think Chisel and firtool view Model and DUT the same, both as a synthesizable module. So how firtool knows the boundary? Need it add new annotation in FIRRTL IR?
Hi All,
We were wondering if it would be possible to support a flag in
firtool
that uniquifies the modules under theDut
andHarness
. When running timing annotated simulations, after theDut
is synthesized the modules that are common to theDut
andHarness
will collide and cause simulation to fail.The related issue is ucb-bar/chipyard#1388 and ucb-bar/chipyard#1422 is a temporary workaround which post-processes the generated verilog files using a python script.
Thanks!
Related people to this issue
@harrisonliew
@abejgonzalez
@allpan3
The text was updated successfully, but these errors were encountered: