• 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
  • diablo
    diablo over 14 years ago

    Hi Bob,

    Thanks for the reply.

    I tried your solution and I have few questions on it. 

    encounter 6> get_property -view func_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks

    0x11692
    encounter 7> get_property -view test_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks

    0x11694
     

    I did not get clock name as in your case.

    I tried the looping through the registers using your foreach loop and replacing correponding views and clock name.  For hierarchical_name i am assuming, i have to replace it with any instance name. This is what i had, but could not get it to run correctly.

    foreach_in_collection register [all_registers] {
      foreach_in_collection pin [filter_collection [get_pins [get_property $register pc0]/*] {is_clock == true}] {
        set clk [get_property [get_property -view func_worst $pin clocks] pc0]
        if {$clk == "CLK5"} {
          Puts "Pin: [get_property $pin pc0] in view \"func_worst\" is driven by \"CLK5\""
        }
      }
    }

    When you have set clk[get_property...], the inner get_property gets the pins but what about the outer get_property? which property is it trying to fetch?

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

    Hi Bob,

    Thanks for the reply.

    I tried your solution and I have few questions on it. 

    encounter 6> get_property -view func_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks

    0x11692
    encounter 7> get_property -view test_worst [get_pins pc0/vreg_ovp_reg_0/CKN] clocks

    0x11694
     

    I did not get clock name as in your case.

    I tried the looping through the registers using your foreach loop and replacing correponding views and clock name.  For hierarchical_name i am assuming, i have to replace it with any instance name. This is what i had, but could not get it to run correctly.

    foreach_in_collection register [all_registers] {
      foreach_in_collection pin [filter_collection [get_pins [get_property $register pc0]/*] {is_clock == true}] {
        set clk [get_property [get_property -view func_worst $pin clocks] pc0]
        if {$clk == "CLK5"} {
          Puts "Pin: [get_property $pin pc0] in view \"func_worst\" is driven by \"CLK5\""
        }
      }
    }

    When you have set clk[get_property...], the inner get_property gets the pins but what about the outer get_property? which property is it trying to fetch?

    • 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