• 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. [Innovus] report the fanout of ICG

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 96
  • Views 13862
  • 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

[Innovus] report the fanout of ICG

hammercui
hammercui over 3 years ago

I am looking for one way to report the ICG fanout status, below pic is the example of the ICG connection

I could get the fanout count of ICG a :

> sizeof_collection [all_fanout -from a -endpoints_only] , then I will get 100+200+300+3(b,c,d)

Now, I want to get the regs count from a: 100; and b's fanout of regs: 200 and c's fanout of regs :300 respectively.

Any comments will be appreciated

  • Cancel
  • hammercui
    hammercui over 3 years ago

    + more, actually I am looking for one way to ask tool to stop tracing at the first sub level ICG when I report the fanout from one point

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DimoM
    DimoM over 3 years ago in reply to hammercui

    Hi,
    all_fanout has the switches  -levels and -pin_levels , which you can use for this purpose.

    -Dimo

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • hammercui
    hammercui over 3 years ago in reply to DimoM

    Thanks Dimo

    But it seems, that the -levels include all kinds of gate, for my case, I hope it by pass all combinational logic .... 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • DimoM
    DimoM over 3 years ago in reply to hammercui

    I see what you mean now.

    The easiest way that comes in mind is to use set_case_analysis on the CP pin of the ICG. Then all_fanout won't trace trough it. 

    E.g.
    set_interactive_constraint_modes [get_db constraint_modes .name]
    set_case_analysis 0 b/CP

    all_fanout -from a -endpoints_only

    # Remove case analysis after that 
    reset_case_analysis b/CP
    set_interactive_constraint_modes {}

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • hammercui
    hammercui over 3 years ago in reply to DimoM

    Hi DimoM

    Thanks for your comments, yes, by this way I could get the end point (fanout) count for each ICG, but the limitation is we can not trace the relationship between ICGs

    I mean, I can not trace : ICG a drives b, and b drives c, and c drives d .....

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • hammercui
    hammercui over 3 years ago in reply to hammercui

    Innovus should provide one feature to report the ICG tree, which only include ICG and other sequential cells

    • 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