Honored Contributor
Honored ContributorI didn't know there was a timing report - I guess I should do a lot more reading before I jump in.
I clicked on a TimeQuest link and copied parts of various reports. They mean nothing to me, but you might be able to see quickly where the problem lies. =============================================================================================== Info: No user constrained base clocks found in the design. Calling "derive_clocks -period 1.0" Info: Deriving Clocks Info: create_clock -period 1.000 -name clk clk Critical Warning: Timing requirements not met Info: Worst-case setup slack is -12.688 Info: Slack End Point TNS Clock Info: ========= ============= ===================== Info: -12.688 -347.450 clk Critical Warning: QSF: Expected ENABLE_CLOCK_LATENCY to be set to 'ON', but it is set to 'OFF' Critical Warning: In SDC, create_generated_clock auto-generates clock latency Info: Generated Test.sdc Info: -------------------------------------------------------- 0 create_timing_netlist -model slow check timing no_clock 0 multiple_clock 0 pos_neg_clock_domain 0 generated_clock 0 virtual_clock 1 no_input_delay 0 no_output_delay 2 partial_input_delay 0 partial_output_delay 0 io_min_max_delay_consistency 0 reference_pin 0 generated_io_delay 0 latency_override 0 partial_multicycle 0 multicycle_consistency 0 loops 0 latches 0 pll_cross_check 0 uncertainty 1 partial_min_max_delay 0 clock_assignments_on_output_ports 0 input_delay_assigned_to_clock 0 [1] -12.688 COUNT[8] COUNT[23] clk clk 1.000 0.000 13.355 . . . . [1000] -3.811 COUNT[9] COUNT[20] clk clk 1.000 0.000 4.478 regards
