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.
You mentioned CDC functional checks which apparently means multiple cycle checks as opposed to the first level static checks.
Functional checks involve resetting flops and proper design set-up before checking. With multiple cycles the potential function can become very compilicated quickly. Especially for a large design like your own.
I don't know if there is a "one size fits all" type of solution in this case. I think the best way to investigate is to contact Cadence support and talk to them. If you find a solution please share it with us!
In reply to tstark:
When you say ''proper design set-up'' what exactly does the checklist cover apart from resetting flops. Could you please elaborate?
In reply to arunvaidya:
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,