-
Notifications
You must be signed in to change notification settings - Fork 42
Add estimate power command to dynamatic #655
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
base: main
Are you sure you want to change the base?
Conversation
shundroid
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for adding this feature!
| # Run synthesis | ||
| synth_design -top $TOP_DESIGN -part xc7k160tfbg484-1 -no_iobuf -mode out_of_context -flatten_hierarchy none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to run the synthesis again? I think it's better to use write_checkpoint and read_checkpoint commands if possible:
syntax:
write_checkpoint -force $DIR/impl.dcp
(read_checkpoint: I've never tried)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the -flatten_hierarchy none flag means that this synthesis run produces different results to the normal synthesis script (poorer results, but it allows the switching activity annotation)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted to mention the duplication with the synthesis for power estimation, I think it also has the flatten_hierarchy option:
| synth_design -top $TOP_DESIGN -part xc7k160tfbg484-1 -no_iobuf -mode out_of_context -flatten_hierarchy none |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, possibly! but we are currently only running synthesis once (some of the simulations were hanging with the double synth option).
I should investigate it though!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah, possibly! but we are currently only running synthesis once (some of the simulations were hanging with the double synth option).
I should investigate it though!
|
|
||
| vhdl_src_folder = os.path.join(output_dir, "hdl") | ||
| if not os.path.exists(vhdl_src_folder): | ||
| print(f"[ERROR] {vhdl_src_folder} not found. Please run the 'write-hdl' command") | ||
| return | ||
|
|
||
| tb_file = os.path.join(output_dir, "sim", "HDL_SRC", f"tb_{kernel_name}.vhd") | ||
| if not os.path.exists(tb_file): | ||
| print(f"[ERROR] {tb_file} not found. Please run the 'simulate' command") | ||
| return |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@shundroid switched so the vhdl files are from the hdl folder, and we pull just the tb file from the sim folder
No description provided.