• 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. RC response[TUI-39]after "report clock_gating"

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 61
  • Views 1287
  • 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

RC response[TUI-39]after "report clock_gating"

cwwang
cwwang over 10 years ago

Hi All,

     After "synthesis -to_mapped",when issuing "report clock_gating" command. The following error message appears:

====== 

Error   : Invalid or missing object for the attribute. [TUI-39] [get_attribute]

        : An object was not specified or the specified object was an invalid object type. There are 4 valid object types that can be specified as the final (third) argument when getting the 'lp_computed_toggle_rate' attribute. Valid objects are: pin, subport, port, and net.

1 

 ======

Although I can still write out the mapped netlist and sdc. But failed at the following command "write_et_atpg".In other words, no atpg database and I could not ignore this error. Someone tell me that RC may encounter some problem while trying to insert gated cell. But the log file did not show such a problem after "synthesis -to_mapped" command. I had checked the netlist and found that cells with RC_CGXX exists. I think that clock gated may works. Would you help me to solve this issue?Or tell me what else could I check.Thanks!

  • Cancel
Parents
  • cwwang
    cwwang over 10 years ago
    Problem solved by Cadence AE. The root cause is that RC10 had a bug while calculating toggle rate of a design with clock gating turned on. This issue had gone while using RC13.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • cwwang
    cwwang over 10 years ago
    Problem solved by Cadence AE. The root cause is that RC10 had a bug while calculating toggle rate of a design with clock gating turned on. This issue had gone while using RC13.
    • 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