-
Notifications
You must be signed in to change notification settings - Fork 551
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
Clock tree appears to be unbalanced for BoomTile running at 833 MHz #5970
Comments
@jeffng-or if you zoom in the leafs on the skewed side you can select them to see what instances they are. |
@jeffng-or Do you know if there are any clock gaters on this design? Clock gaters have some issues currently. |
AFAIK, no clock gaters. The only cells used in the clock tree look to be bufs or invs: (BUFx10_ASAP7_75t_R) |
The far right branch connects to one macro: dcache/data/array_1_0_ext/R0_clk. The other long branch nearer to the middle of the clock tree is clknet_leaf_402_clock_regs, which connects to:
|
It branches off the tree very high up. If you look at where it branches do you see a gate? |
I don't think so. I checked the connections at the colored dots in the clock tree:
In case you want to look at the clock tree in more detail, I have the output from a clock tree connectivity dumper that I wrote (no guarantee that it's totally correct). The output is a text file which can be found in: https://drive.google.com/file/d/1bL4rkNu9erDrZYoNKofA7MbXbJbnxByT/view?usp=sharing |
@arthurjolo is this due to splitting macros from std cells? |
I am going to open the design and take a close look on it, but I don't think this is due to the splitting of macros from std cells. On the macros branch Jeff mentioned that there are delay buffer so the average arrival time on the macro branch was smaller then on the std cells, so the other macros seem to have a better arrival time. I believe that CTS did a poor job connecting to dcache/data/array_1_0_ext/R0_clk, I am going to try to understand why. |
One thing that I noticed from Jeff's dump is that on the |
Describe the bug
For megaboom v6, I upped the clock frequency to 833 MHz and the resulting clock tree appears to be unbalanced (see the branch of the tree on the far right in the viewer) and with significant skew:
Tom mentioned that sometimes the clock tree will be unbalanced when connecting to macros, so I'd like to get some feedback on whether that's the case here. Note that prior versions of BoomTile with a slower clock generated a balanced clock tree with not as much skew.
Expected Behavior
Balanced clock tree with minimal skew
Environment
To Reproduce
I kept 3_place.odb in the tarball in case it's helpful.
Relevant log output
No response
Screenshots
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: