• 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 taking too much time.

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 62
  • Views 14016
  • 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 taking too much time.

arunvaidya
arunvaidya over 13 years ago
Hi there,

I am currently engaged in closure of CDC functional checks but to my frustration the run for CDC functional checks is taking a great deal of time and till now its just too slow to see it finish. I would like to know if there is any way on how I may investigate this problem and hopefully speed the runtime considerably. The design has a gate count of around 2.8 million.

FYI: There are no errors received during the run.
  • Cancel
Parents
  • arunvaidya
    arunvaidya over 13 years ago

    I was instructed (by email, post not in forum) to clear up structural violations and once I was able to clear all the structural violations in the design I fired a run to perform all the functional CDC checks. The total run time taken was approx. 5-6 days, but to my suprise most (95%) of the checks returned a status of ED (explored depth), indicating a higher prove effort is required (but atleast the run finished with some results).

    If I do increase prove effort won't it increase the already long run time or are there any other suggestions on how I may proceed to reduce the run time by also reducing the total number of ED paths.

    Thanks for the help,

    Arun V.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • arunvaidya
    arunvaidya over 13 years ago

    I was instructed (by email, post not in forum) to clear up structural violations and once I was able to clear all the structural violations in the design I fired a run to perform all the functional CDC checks. The total run time taken was approx. 5-6 days, but to my suprise most (95%) of the checks returned a status of ED (explored depth), indicating a higher prove effort is required (but atleast the run finished with some results).

    If I do increase prove effort won't it increase the already long run time or are there any other suggestions on how I may proceed to reduce the run time by also reducing the total number of ED paths.

    Thanks for the help,

    Arun V.

    • 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