• 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. Issue with gated clock

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 61
  • Views 14194
  • 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

Issue with gated clock

archive
archive over 18 years ago

Hi,
I am doing a c omparison of RTL vs. gate. The original RTL has some clock gating that has been instantiated using technology library gate elements. During sytnhesis further clock gatignf has been added by synthesis tool.
Consequently I have used "set flatten model -gated_clock' to be able to process gated clock elements.
Unfortunately some points miscompated due to the fact that in golden (RTL) design the gated clock appears in the fanin cone of the FF while in the revised does not.
Did I make some wrong switches ?

Thanks
Maurizio


Originally posted in cdnusers.org by maurizios
  • Cancel
Parents
  • archive
    archive over 18 years ago

    I have did several trials. The bottom line seems to be the following;
    - There is a clock gating structure in RTL Code
    - I used the flattening option "set_flatten_mode -gated_clock"
    - The gating elements are properly mapped in both golden and revised netlist.
    When I am trying to diagnose a not-comparing points the cause of miscomparison seems to be the fact that for golden netlist clock itself and gating element are in the fanin cone but this is not true for revised netlist ( see line below0):
    There are extra but mapped key points in this logic cone
    ================================================================================
    ID Type Name
    --------------------------------------------------------------------------------
    (G) + 63763 'DLAT' /i_nocino_core/i_cpu_domain/i_VCPU_ClkCtrl/i_GrappaRefClkGate/Enable_Latch_reg
    (G) + 63978 Nocino_analog_top:'PIN' /i_nocino_core/tvdd_domain0/i_nocino_analog_top/SCK
    ================================================================================

    The tool finds then a failing pattern by applying a 0 to SCK
    Does anybody have an idea why this is happening?
    Thamks
    Maurizio


    Originally posted in cdnusers.org by maurizios
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    I have did several trials. The bottom line seems to be the following;
    - There is a clock gating structure in RTL Code
    - I used the flattening option "set_flatten_mode -gated_clock"
    - The gating elements are properly mapped in both golden and revised netlist.
    When I am trying to diagnose a not-comparing points the cause of miscomparison seems to be the fact that for golden netlist clock itself and gating element are in the fanin cone but this is not true for revised netlist ( see line below0):
    There are extra but mapped key points in this logic cone
    ================================================================================
    ID Type Name
    --------------------------------------------------------------------------------
    (G) + 63763 'DLAT' /i_nocino_core/i_cpu_domain/i_VCPU_ClkCtrl/i_GrappaRefClkGate/Enable_Latch_reg
    (G) + 63978 Nocino_analog_top:'PIN' /i_nocino_core/tvdd_domain0/i_nocino_analog_top/SCK
    ================================================================================

    The tool finds then a failing pattern by applying a 0 to SCK
    Does anybody have an idea why this is happening?
    Thamks
    Maurizio


    Originally posted in cdnusers.org by maurizios
    • 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