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

Issue with interpreting outputs #2062

Open
cansudemirkiran opened this issue Oct 26, 2023 · 1 comment
Open

Issue with interpreting outputs #2062

cansudemirkiran opened this issue Oct 26, 2023 · 1 comment

Comments

@cansudemirkiran
Copy link

Hi,

I have been testing the tool, and I have a few questions. When I feed different Verilog files into the tool or use different targets, even though I receive no errors, I sometimes can't collect all the output values, or they appear inconsistent. I use the '-remote' option for running jobs.

For example, when I run a Verilog file for a simple MAC unit with 'freepdk45' as the target, I can collect all the outputs from all the steps except 'export0'. When I run the same Verilog file with the 'asap7' target, I can complete the run without any errors, but I no longer get 'Fmax' and area information on the PNG file. The 'export 1' column also disappears.

It's also odd that the power numbers for the 7 nm library are more than ten times larger than the 45 nm numbers while running at a similar clock frequency. The 7 nm output shows a negative slack, I assume this means that the design does not meet the requirements. However, the clock period I defined in the constraint file was 10 ns, whereas the Fmax for this design appears to be over 1 GHz. Also, I expected the 7 nm design to be capable of running faster.

I've attached screenshots for these two cases, I'd greatly appreciate your feedback on how to interpret this. Thank you!

Screenshot 2023-10-26 at 7 11 45 PM Screenshot 2023-10-26 at 7 20 54 PM
@cansudemirkiran cansudemirkiran changed the title Issue with Interpreting Outputs Issue with interpreting outputs Oct 26, 2023
@gadfort
Copy link
Contributor

gadfort commented Nov 17, 2023

@cansudemirkiran sorry for the delay. Both of these PDKs are virtual, so some of their behavior is going to be inconsistent. There are some setup differences between the two libraries (this is the only reason I can think of at the moment):

  • freepdk45 only has a single timing and parasitic corner enabled (typical only), which will result in more ideal answers.
  • asap7 has three corners enabled (slow, typical, and fast), so that would be one reason you end up seeing similar performance despite how much faster asap7 should have been.

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

2 participants