Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 15004
  • 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

CDC Methodology

sureshm

Hi All,

I am using the CCD tool for my CDC methodology. But the information about the commands & the explanations given in the documentation is very limited with respect to the explanation.

I  would like to explain the problem/requirement to see the issues from my deisgn

1) How to mention/get all the signal cross overs in a report which are not passing  through the specified user sync modules?

2) how to specify multiple sync modules to the design/ cdc rule set ?

3) How to generate waiver file and how to feed  the waiver file to the CDC tool?

Any inputs on the CDC methodology is highly appreciated. !!!

 

Thanks

suresh

 

Parents
  • Suresh
     
    Add rule filter is the recommended way over "add rule waiver" going forward to perform what you would need based on your descriptions below. It supports a lot more different options which allows users to filter out certain violations in the reports.
     
    Add rule filter supports
     
           ADD RUle Filter
           <filter_name> [<condition ...>]
           [-DESCription <description>]
           [-RULe <rule_name*>] ...
           [-REPlace]

    <condition> -SEVerity <name> -MESsage <pattern*> -OBJect [-Hierarchical] [-Recursive] <name*> -SDCMatch <pattern*> -AND -OR -OCCurrence < "[occurrence#] [ ' .. ' ] [occurrence#]" > -SDC_MODE <mode_name> -SDC_DESIGN <design_name>

    This is just an excerpt from the man pages and you can find detailed descriiptions + examples from the reference manual.

    Based on what you mentioned below, you should be able to filter out the violations using -sdc_design and -rule.  If you need further assistance with using this command for your design, please contact your local AE.

    As for the excerpt for the report you attached in your email,

    structural : cdc_path_logic_type_check            : LOGIC          : Fail  <--- This means that CCD found logic instances on your CDC path, which is a failure, because you specified either wire or buffer in the settings. By default, CCD allows only wire on the CDC path. You can control this using the attribute cdc_path_logic
    structural : cdc_path_destination_check           : MULTIPLE       : Fail <---- This means that CCD detacted multiple destinations on your CDC path, whereas only single destination is allowed per your specification. Single destination is the default. You can control this using the attribute cdc_path_fanout.

    Again there is more info about the atomic checks and the attributes I mentioned above in the reference manual. Please take a look.

    Thanks, Jack
Reply
  • Suresh
     
    Add rule filter is the recommended way over "add rule waiver" going forward to perform what you would need based on your descriptions below. It supports a lot more different options which allows users to filter out certain violations in the reports.
     
    Add rule filter supports
     
           ADD RUle Filter
           <filter_name> [<condition ...>]
           [-DESCription <description>]
           [-RULe <rule_name*>] ...
           [-REPlace]

    <condition> -SEVerity <name> -MESsage <pattern*> -OBJect [-Hierarchical] [-Recursive] <name*> -SDCMatch <pattern*> -AND -OR -OCCurrence < "[occurrence#] [ ' .. ' ] [occurrence#]" > -SDC_MODE <mode_name> -SDC_DESIGN <design_name>

    This is just an excerpt from the man pages and you can find detailed descriiptions + examples from the reference manual.

    Based on what you mentioned below, you should be able to filter out the violations using -sdc_design and -rule.  If you need further assistance with using this command for your design, please contact your local AE.

    As for the excerpt for the report you attached in your email,

    structural : cdc_path_logic_type_check            : LOGIC          : Fail  <--- This means that CCD found logic instances on your CDC path, which is a failure, because you specified either wire or buffer in the settings. By default, CCD allows only wire on the CDC path. You can control this using the attribute cdc_path_logic
    structural : cdc_path_destination_check           : MULTIPLE       : Fail <---- This means that CCD detacted multiple destinations on your CDC path, whereas only single destination is allowed per your specification. Single destination is the default. You can control this using the attribute cdc_path_fanout.

    Again there is more info about the atomic checks and the attributes I mentioned above in the reference manual. Please take a look.

    Thanks, Jack
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.