• 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. Logic Design
  3. defined clocks not propagate

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 63
  • Views 14046
  • 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

defined clocks not propagate

tompy
tompy over 14 years ago

I have a design with clocks defined at root.I can use [get_attrbute  propagated_clocks] to get clock propagate at g152/Z,

however, I cannot get propagated clock at g151/Z

  XOR2D0HVT g151(.A1 (n_2), .A2 (clk2), .Z (clk2_inv));
  XOR2D0HVT g152(.A1 (n_2), .A2 (clk1), .Z (clk1_inv));

 I can also get propagated clock at g151/A2 and g152/A2

this is pretty weird since g151 and g152 are same logic, but I can't get propagated clock at g151 output!

can someone tell me why g151 block the clock propagation? thanks!

 

  • Cancel
Parents
  • grasshopper
    grasshopper over 14 years ago

     Hi Tompy,

     hard to tell based on the information provided. Some issue that could possibly do this:

     + edit_neltist command on output of g151

    + constraint applied to output resulting on path segmentation

    BTW, are you hand-instantiating g151 and g152. What does incoming RTL look like ? What do incoming constraints look like ?

     

    thanks,

    gh-

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • grasshopper
    grasshopper over 14 years ago

     Hi Tompy,

     hard to tell based on the information provided. Some issue that could possibly do this:

     + edit_neltist command on output of g151

    + constraint applied to output resulting on path segmentation

    BTW, are you hand-instantiating g151 and g152. What does incoming RTL look like ? What do incoming constraints look like ?

     

    thanks,

    gh-

    • 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