<@U0172QZ342D> I would say an STA report has 4 sec...
# timing-closure
t
@Matt Venn I would say an STA report has 4 sections 1) Insertion delay to startpoint 2) (Adding) delay btw startpoint and endpoint => data arrival time 3) Insertion delay to endpoint (adding clock period for max) => data required time 4) Calculations of slack using data arrival time, data required time, setup|hold time => slack If you want to skip insertion delay report (-no_splash option possibly???), or if you are in an idealistic world on RTL, then section 1) and 3) are not shown or are 0. The starting point is an input as your second last pic indicates, so the insertion delay to the startpoint is 0. Look at it as if the external input is "clocked" by the same clock to fit into this reporting scheme. I assume that you have an input delay set somewhere, which is 10 ns. But that is only a guess based on the report. For this input to register line the data arrival time = input delay. The clock period is 10 ns (I guess), it shows up because it is a max report, and the DFF insertion delay is 0, so the data required time is 10. The calculations I mentioned above. So I would play with the clock period (e.g. 9 ns) or the input delay (e.g. 12 ns) to see how that affects the report. PS: Always nice to have these discussions within one thread for reference.
🙌 1
m
thanks Tobias
agree about the threading, sorry about that
m
which of the segments is shown is controlled by [-format end|full|short|summary |full_clock|full_clock_expanded]