18:41 <Sarayan> Lofty, I'm going to need your help on timings. I have a lot of information but I'm not entirely sure how it's supposed to be used. And the problem is that I don't see how I could try to reproduce what quartus does simply because I don't know how to have it give me useful information. Do you know how to get delays on a given path, this kind of stuff?

18:41 <Sarayan> I don't have the energy available to really try to understand how to use quartus in that area

18:54 <Lofty> Sarayan: so, my usual approach is to open up the timing analyser on a design, and there's then an option to show the critical paths. That actually lets you choose things like critical paths through a wire, and also shows you the equivalent TCL command

18:58 <Sarayan> ok, let's try that

18:58 <Sarayan> first I recompile so that everything is in sync

18:59 <Sarayan> ok, timing analyzer open, I need to create a timing netlist I guess?

19:01 <Sarayan> and then I'm lost

19:07 <Sarayan> Each time I'm trying to get info on a path I'm getting "nothing to report"

19:08 <Sarayan> og.kervella.org/mini.zip is the design I use

20:05 <Sarayan> ok report_timing -show_routing -file t seems to give interesting information