• 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. set_clock_group behavior - SOC81USR3

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 1743
  • 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

set_clock_group behavior - SOC81USR3

Vishnu Chada
Vishnu Chada over 15 years ago

 Hi,

 

PLL --(CLK)--------------------------DIVIDER ---(gen_CLK1)---------------------------FLOP_GROUP1

                       |______DIVIDER ---(gen_CLK2)----------------------------FLOPS_GROUP2

 

I have two generated clocks from master clock CLK as pictured above.

When i define  CLK and gen_CLK2  as asynchronous clock groups i intend not to see timing paths between FLOP_GROUP1 and FLOP_GROUP2. When i load this constraint in encounter i see otherwise.

set_clock_groups -name group1 -asynchronous  -group  [get_clocks {CLK}] -group  [get_clocks {gen_CLK2}]

 I see a timing path between these flop groups clocked by generated clocks reported by encounter.

Is it not implicit that gen_CLK1 and gen_CLK2 are also asynchronous clock groups ?

Is there a switch i should use to see this behaviour with CTE ?

Appreciate your time.

Regards,

Vishnu

  • Cancel
Parents
  • Vishnu Chada
    Vishnu Chada over 15 years ago
    Thanks for the response kari. Looks like i just need to add the generated clock to the same group as the master clock to see this behaviour. Regards, Vishnu
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Vishnu Chada
    Vishnu Chada over 15 years ago
    Thanks for the response kari. Looks like i just need to add the generated clock to the same group as the master clock to see this behaviour. Regards, Vishnu
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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