• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Balance Clock Tree Skew and levels of two different Block...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 16047
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Balance Clock Tree Skew and levels of two different Block implementation in Encounter

sachintaneja
sachintaneja over 7 years ago

Hello everyone, 

I have two blocks separately implemented using the Encounter.


They have huge CTS Global skew and i am unable to balance the CTS of two blocks and having hold violations between the very shallow paths having communication between the blocks.


This is due to the number of logic elements in the two block. One block has 160 FF and simple in design and other has 550 and complex block in terms of logic.

Block 1 : CTS : 1 level : Min Trig Skew: 20 ps , Max Trig Skew: 40ps
Block 2 : CTS : 5 level : Min Trig Skew: 300 ps , Max Trigger Skew: 400ps

It will be helpful if you someone can share how to balance (small skew can he handled in post silicon tuning) the CTS of two blocks to avoid top level CTS flow as i want different clock port for both blocks.

It will helpful if any reference to balance the CTS in hierarchical design (current implementation) and top level CTS (future implementation) can be shared.

Thanks,
Sachin

  • Cancel
  • Kari
    Kari over 7 years ago

    Been a while since we did that, but at the top, you use MacroModel statements in the CTS instructions, which will have the insertion delays of each block, so the top knows how to balance them.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information