Tuesday, 2021-05-04

*** tpb has joined #symbiflow00:00
*** Degi has quit IRC00:15
*** Degi has joined #symbiflow00:16
*** gsmecher has quit IRC00:18
*** citypw has joined #symbiflow02:40
*** citypw has quit IRC03:44
*** TMM has quit IRC04:41
*** TMM has joined #symbiflow04:41
*** citypw has joined #symbiflow05:27
sf-slack1<fdarling> Do you know of someone (maybe you?) who'd be willing to get support for the Artix-7 chip on the MicroNova Mercury 2 FPGA if I were to gift them a board?06:50
sf-slack1<fdarling> it wasn't available on SciHub either, so I am guessing (like Chander said) that it isn't in circulation yet06:54
*** jonfl has quit IRC07:43
*** citypw has quit IRC07:44
*** adjtm_ has quit IRC10:04
*** citypw has joined #symbiflow10:52
*** citypw has quit IRC11:05
sf-slack1<cjearls> I'd be happy to help add support for it. Is there no support for it at all in SymbiFlow currently, or is there just no example in the symbiflow-examples repo?11:13
*** citypw has joined #symbiflow12:06
-_whitenotifier-3- [nextpnr] gatecat opened issue #287: [interchange] Site pin conflicts in RAM test - https://git.io/J3atP13:22
*** citypw has quit IRC14:31
*** maartenBE has quit IRC15:02
*** maartenBE has joined #symbiflow15:04
*** calphool has joined #symbiflow15:20
calphoolHello all, question: how does timing analysis work with the Symbiflow tool chain?15:21
*** gsmecher has joined #symbiflow15:58
Loftycalphool: As I understand it both VPR and nextpnr output the critical path16:07
sf-slack1<calphool> My experience is mostly in Quartus.  So in there you set timing constraints in the sdc file.  Then when you do the place and route you get a timing analysis report where it tells you whether you were able to achieve the constraints you provided, and somehow the tool knows what's achievable across temperature ranges and so on.  I was under the impression that that stuff was proprietary to Quartus for its known chip16:14
sf-slack1set.  Are those physical characteristics part of what's in the open?16:14
calphoolSorry.. I am running both Slack and IRC... calphool = JR16:15
LoftySo, uh16:18
LoftyIntel stuff comes under Project Mistral, of which I am project lead16:18
LoftyIt's not technically a Symbiflow project16:19
LoftyAnyway, the long and short of it is that while they're not in the open, you can obtain that timing information by looking at the output of quartus_sta on a netlist16:22
LoftyAnd if you correlate these with the paths, you now have path timings16:23
*** calphool has quit IRC16:25
umarcoris it possible to do fine-grained placement with Yosys + nextpnr? i.e. tell which specific BRAM block(s) to use when inferring some memory, and let the tools handle all the rest of the placement and routing.16:44
umarcorthe use case is having multiple designs/bitstreams which all share the same specific BRAM block.16:44
Loftyumarcor: https://github.com/YosysHQ/nextpnr/blob/master/docs/constraints.md#absolute-placement-constraints16:47
umarcorLofty: thanks!16:48
mithro@acomodi: New prjxray-db push with the new DSP pips - https://github.com/SymbiFlow/prjxray-db/compare/master...mithro:master17:27
*** rj has joined #symbiflow17:27
mithrogatecat: Need anything from me regarding the interchange format stuff?17:31
gatecatmithro: you could give https://github.com/SymbiFlow/python-fpga-interchange/pull/80 a review if you want? otherwise I think all is good17:32
mithrocalphool - VPR outputs a timing report17:32
mithrocalphool: VtR also supports timing constraints -> https://docs.verilogtorouting.org/en/latest/vpr/timing_constraints/17:32
tpbTitle: Timing Constraints Verilog-to-Routing 8.1.0-dev documentation (at docs.verilogtorouting.org)17:33
mithroAccording to https://docs.verilogtorouting.org/en/latest/vpr/debug_aids/ -- The report_timing.setup.rpt file lists details about the critical path of a circuit, and is very useful for determining why your circuit is so fast or so slow.17:33
tpbTitle: Debugging Aids Verilog-to-Routing 8.1.0-dev documentation (at docs.verilogtorouting.org)17:33
mithrogatecat: There are a number of BYU students who want to look at graph folding with the interchange format17:37
gatecatmithro: excellent17:37
gatecatI'm happy to answer questions/discuss ideas if they want17:38
mithrogatecat: I've invited Brent (their supervisor) to the interchange format meeting on Thursday morning17:38
*** rj has quit IRC17:50
*** rj has joined #symbiflow17:55
*** sorear has quit IRC17:58
*** davidlattimore has quit IRC17:59
*** _florent_ has quit IRC18:01
*** davidlattimore has joined #symbiflow18:01
*** sorear has joined #symbiflow18:02
*** _florent_ has joined #symbiflow18:03
*** rj has quit IRC18:34
*** rj has joined #symbiflow18:37
*** kgugala_ has joined #symbiflow18:57
*** kgugala has quit IRC19:00
*** kgugala has joined #symbiflow19:10
*** kgugala_ has quit IRC19:13
*** kgugala_ has joined #symbiflow19:14
*** kgugala has quit IRC19:15
*** kgugala has joined #symbiflow19:15
*** rj has quit IRC19:17
*** kgugala_ has quit IRC19:18
*** rj has joined #symbiflow19:22
*** kgugala_ has joined #symbiflow19:23
*** kgugala__ has joined #symbiflow19:26
*** kgugala_ has quit IRC19:26
*** kgugala has quit IRC19:27
*** kgugala__ has quit IRC19:37
*** kgugala has joined #symbiflow19:37
*** maartenBE has quit IRC19:50
*** maartenBE has joined #symbiflow19:56
*** rj has quit IRC20:02
*** rj has joined #symbiflow20:07
*** rj has quit IRC20:46
*** TMM has quit IRC20:50
*** TMM has joined #symbiflow20:50
*** rj has joined #symbiflow20:51
*** rj has quit IRC21:29
*** rj has joined #symbiflow21:33
*** adjtm has joined #symbiflow22:01
*** rj has quit IRC22:13
*** rj has joined #symbiflow22:19
*** kgugala has quit IRC22:20
sf-slack1<jgoeders> It seems master on https://github.com/SymbiFlow/fasm is broken?  I don't see any issue about it, but it's been that way for a while so I thought I would mention it here.22:51
*** rj has quit IRC22:59
*** rj has joined #symbiflow23:03
sf-slack1<cjearls> I just ran into the same issue on Ubuntu 20, then saw that the Project X-Ray docs  give instructions for Ubuntu 16.04, so I made a virtual machine, and I'm still getting an error when trying to make the environment23:28
*** rj has quit IRC23:38
*** rj has joined #symbiflow23:38
sf-slack1<jgoeders> Interestingly when I go back to an older fasm commit that passed CI I seem to be getting the same error.  So perhaps some antlr dependency has changed.  ...I'm still looking into it.23:43
*** rj has quit IRC23:43
*** rj has joined #symbiflow23:44

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!