In my design, I have a generated clock. I set "set_ccopt_property sink_type stop -pin top/clk_div_gen_reg[0]/CP". Then, the Innovus tool issues a warning as follows:
**WARN: (IMPCCOPT-4142): Could not find a parent clock tree for generated clock div_clk2. Creating a non-generated clock tree.
what happens if you just create the clocks on SDC and leave the ccopt properties untouched? in most cases I have found that the tool is smart enough to handle generated clocks automatically.
what happens if you just create the clocks on SDC and leave the ccopt properties untouched? in most cases I have found that the tool is smart enough to handle generated clocks automatically.
no no, I mean on the SDC file you should describe all the clocks, generated or otherwise. and let the ccopt tool pick up the information from there. it usually works and requires no ccopt_* changes.
no no, I mean on the SDC file you should describe all the clocks, generated or otherwise. and let the ccopt tool pick up the information from there. it usually works and requires no ccopt_* changes.
Sure, I defined all the generated and master clocks in the SDC. After synthesizing, DC writes out an SDC. Then, Innovus uses that SDC. I do not change anything.