--- Quote Start ---
When I run the Name Finder tool in TimeQuest using the get_keepers command, the tool does not report back a clock net for a generated clock in the hierarchy. In fact, it appears as if the clock generator block has been optimized out by the synthesis tool, but I cannot find a reference to this in the synthesis report.
--- Quote End ---
I know you've solved the problem that started this thread, but here are suggestions for finding clocks.
The Fitter compilation report lists clocks at "Resource Section --> Control Signals". I sort the table by clicking the "Usage" column header to list all the clocks together. These clock signals might not correspond exactly to the signal TimeQuest considers to be a clock. For example, a clock driven by a register followed by a LUT will have the LUT signal name in the Fitter report but the register name in the TimeQuest reports. The Fitter's list of clocks is good to look at to see which signals are directly driving the clock input pins of registers. This is one way to find things like unintended gated clocks, which TimeQuest doesn't report. (TimeQuest reports ripple, or register-driven, clocks but not gated clocks.)
To find the TimeQuest name of a clock signal that is not yet constrained, there are a couple of reports you can use.
"Report Unconstrained Paths" (report_ucp) will list unconstrained clocks in the "Clock Status Summary" table.
"Check Timing" (check_timing) will list unconstrained clocks in the "No Clock" table. The clock signals will be the rows with this in the "Reason" column: "Node was determined to feed a clock port but was found without an associated clock assignment."
Honored Contributor
