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

  • Hi   Jack, 

    Thanks for the reply. However, i wasn't clear on the filter & waivers.

    Can you elaborate little more on

    add rule filter & add rule waiver ? 

    Also, I have a module cdc_m1 ( which may not be sync module,) and i want all the signal cross overs through cdc_m1 said to be waiver and i want that report for my design team review ? what is the way to enable this in CCD tool ??

    Further,  

        Below is the sample report that we had seen from one of the reports

    my understanding of user sync module is that any sync module seen in the signal cross over path, it is a PASS. However below report shows Fail, because of the atomic checks ?  what are these atomic checks to do with when user specifying the sync module. ?

     

    please explain the above based on the below report.

     

     

      30:     Fail   : Crossing <inst1>/<inst2>/a_reg ->  <inst1>/<inst3>../<ins5>/b_reg
    |        path_type           : cdc_dff
    |        from_instance       :|  <inst1>/<inst2>/a_reg       to_instance         : <inst1>/<inst3>../<ins5>/b_reg
    |        atomic_checks       : Total 3
    |          structural : cdc_path_logic_type_check            : LOGIC          : Fail
    |          structural : cdc_path_destination_check           : MULTIPLE       : Fail
    |          structural : cdc_user_sync_module_check           : CDC_PULSE_SRC_LOGIC: Pass
     

    Thanks

    suresh

     

     

     

     

Reply

  • Hi   Jack, 

    Thanks for the reply. However, i wasn't clear on the filter & waivers.

    Can you elaborate little more on

    add rule filter & add rule waiver ? 

    Also, I have a module cdc_m1 ( which may not be sync module,) and i want all the signal cross overs through cdc_m1 said to be waiver and i want that report for my design team review ? what is the way to enable this in CCD tool ??

    Further,  

        Below is the sample report that we had seen from one of the reports

    my understanding of user sync module is that any sync module seen in the signal cross over path, it is a PASS. However below report shows Fail, because of the atomic checks ?  what are these atomic checks to do with when user specifying the sync module. ?

     

    please explain the above based on the below report.

     

     

      30:     Fail   : Crossing <inst1>/<inst2>/a_reg ->  <inst1>/<inst3>../<ins5>/b_reg
    |        path_type           : cdc_dff
    |        from_instance       :|  <inst1>/<inst2>/a_reg       to_instance         : <inst1>/<inst3>../<ins5>/b_reg
    |        atomic_checks       : Total 3
    |          structural : cdc_path_logic_type_check            : LOGIC          : Fail
    |          structural : cdc_path_destination_check           : MULTIPLE       : Fail
    |          structural : cdc_user_sync_module_check           : CDC_PULSE_SRC_LOGIC: Pass
     

    Thanks

    suresh

     

     

     

     

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.