• 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. Logic Design
  3. CDC functional checks are not validated for design.

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 63
  • Views 15583
  • 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 functional checks are not validated for design.

vaizguy
vaizguy over 13 years ago

Hello everyone, I was recently required to perform both structural CDC checks and functional CDC checks on a design but when I go through the reports I noticed that the structural checks are performed fine but the functional reports simply say that the paths are not validated. I would like to know why these functional checks aren't being performed as there are no warnings in the log indicating why. Even the GUI has a question mark next to the functional checks tab. while the structural checks has a green/red dot next to it indicating pass/fail resp.

The tool is unable to detect direct bus synchronization instances like the following example and I was hoping that performing functional checks especially the single_bit_change check would highlight all such paths.

Eg.
input [3:0] A; // In clkA domain.
reg [3:0] B_r;
output reg [3:0] B_rr; // In clkB domain.

always @(posedge clkB) begin
  B_r <= A;
  B_rr <= B_r; // This is fine when A is a single bit.
end

Thanks in advance.

  • Cancel
Parents
  • clay
    clay over 13 years ago
     Your dofile should look something like this:

    set log file cdc.log -replace                                      

    set flatten model -noncontrolling_remodel

    add search path rtl

    read design rtl/fsm.v s_d_data.v sync.v top.v

    set clock_domain rule -extract -noderived

    add pin constraint 1 rstan

    add pin constraint 1 rstbn

    add clock 0 -waveform 1 1 2 clka

    add clock 0 -waveform 3 3 6 clkb

    read initial state init.seq

    set system mode verify

    add sync rule dff -dff 2 -sync_chain buffer single_chain -cdc_path buffer single_destination

    add sync rule mux -mux 0 0 -hold -cdc_path buffer single_destination

    add cdc check -structural -source -all -destination -all -from -all -to -all

    validate

    add cdc check -functional -source -all -destination -all -from -all -to -all

    validate

     

    Is this what you basically have?

    Let me know.

    Regards,  Clay
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • clay
    clay over 13 years ago
     Your dofile should look something like this:

    set log file cdc.log -replace                                      

    set flatten model -noncontrolling_remodel

    add search path rtl

    read design rtl/fsm.v s_d_data.v sync.v top.v

    set clock_domain rule -extract -noderived

    add pin constraint 1 rstan

    add pin constraint 1 rstbn

    add clock 0 -waveform 1 1 2 clka

    add clock 0 -waveform 3 3 6 clkb

    read initial state init.seq

    set system mode verify

    add sync rule dff -dff 2 -sync_chain buffer single_chain -cdc_path buffer single_destination

    add sync rule mux -mux 0 0 -hold -cdc_path buffer single_destination

    add cdc check -structural -source -all -destination -all -from -all -to -all

    validate

    add cdc check -functional -source -all -destination -all -from -all -to -all

    validate

     

    Is this what you basically have?

    Let me know.

    Regards,  Clay
    • 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