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

Reporting non-RC gated flops

Max Bjurling over 2 years ago

The report_clock_gating command prints out a summary of the number of RC-gated flops, non-RC-gated flops, and ungated flops. Using the -gated_ff or -ungated_ff options the commands prints details about the gated or ungated flops.

Is there a way to get details about the non-RC gated flops without getting the details about all gated flops? Typically this report becomes very long if all gated flops in a design are listed (as with the -gated_ff option).

Dimo M over 1 year ago

Hi Max,

as outlined in the article What does “Non-RC Gated Flip-flops” imply in the clock gating report? :

"To see whether the flop is gated by user/Genus inserted CG instance, you can use the lp_clock_gating_is_flop_user_gated and lp_clock_gating_is_flop_rc_gated attribute respectively.
...
Example:
get_db insts -if {.lp_clock_gating_is_flop_user_gated==true}
In Legacy_UI:
filter lp_clock_gating_is_flop_user_gated true [find / -inst *]
"

Dimo
Cancel
Up +1 Down

Cancel
Max Bjurling over 1 year ago in reply to Dimo M

Thanks Dimo, that was the solution to my problem!

/Max
Cancel
Up 0 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.

Stats

Reporting non-RC gated flops

Community Guidelines