Skip to content
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

[FIRRTL] Dut and Harness separation flag for firtool #5066

Open
joonho3020 opened this issue Apr 21, 2023 · 2 comments
Open

[FIRRTL] Dut and Harness separation flag for firtool #5066

joonho3020 opened this issue Apr 21, 2023 · 2 comments

Comments

@joonho3020
Copy link

joonho3020 commented Apr 21, 2023

Hi All,

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.

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

@davidmlw
Copy link

davidmlw commented Jul 3, 2023

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?

@tymcauley
Copy link
Contributor

@joey0320 I think the PR link in the issue description should be ucb-bar/chipyard#1442 rather than 1422.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants