• 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. How to report list of flops whose clock port is driven by...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 91
  • Views 18821
  • 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

How to report list of flops whose clock port is driven by test clock in test mode

diablo
diablo over 14 years ago

 Hi all,

  I have functional and test analysis views. The Test clock is muxed with functional clock whose selector is TEST_EN net.

  In my functional SDC, I have "set_case_analysis 0 TEST_EN" and in test SDC, I have "set_case_analysis 1 TEST_EN". I want to verify  whether in test analysis view, the Test clock is seen by all the flops. 

  How to report the list of flops whose clock port is driven by test clock in test analysis view.

 Thanks for your time.

  

 

  • Cancel
Parents
  • BobD
    BobD over 14 years ago

    Hmm - that's strange that it appears to be returning a collection, but the name of the clock isn't echoed.

    "get_proeprty [get_pins xxx] clocks" should get a collection of clocks.  To query the name of those clocks we need to:

    get_property [get_property -view func_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks] hierarchical_name

    -or- if there are multiple clocks you could iterate through each like this:

    foreach_in_collection clk [get_property -view func_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks] {puts "[get_property $clk hierarchical_name]"}

    "hierarchical_name" is an attribute off clocks and other objects alike so you shouldn't have to swap out hierarchical_name for instance_name.  The outer get_property returns the name, the inner get_property returns a collection.

    Let us know how these suggests enlighten things and we can go from there.

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

    Hmm - that's strange that it appears to be returning a collection, but the name of the clock isn't echoed.

    "get_proeprty [get_pins xxx] clocks" should get a collection of clocks.  To query the name of those clocks we need to:

    get_property [get_property -view func_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks] hierarchical_name

    -or- if there are multiple clocks you could iterate through each like this:

    foreach_in_collection clk [get_property -view func_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks] {puts "[get_property $clk hierarchical_name]"}

    "hierarchical_name" is an attribute off clocks and other objects alike so you shouldn't have to swap out hierarchical_name for instance_name.  The outer get_property returns the name, the inner get_property returns a collection.

    Let us know how these suggests enlighten things and we can go from there.

    • 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