*** tpb has joined #symbiflow | 00:00 | |
*** Degi has quit IRC | 00:15 | |
*** Degi has joined #symbiflow | 00:16 | |
*** gsmecher has quit IRC | 00:18 | |
*** citypw has joined #symbiflow | 02:40 | |
*** citypw has quit IRC | 03:44 | |
*** TMM has quit IRC | 04:41 | |
*** TMM has joined #symbiflow | 04:41 | |
*** citypw has joined #symbiflow | 05: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 yet | 06:54 |
*** jonfl has quit IRC | 07:43 | |
*** citypw has quit IRC | 07:44 | |
*** adjtm_ has quit IRC | 10:04 | |
*** citypw has joined #symbiflow | 10:52 | |
*** citypw has quit IRC | 11: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 #symbiflow | 12:06 | |
-_whitenotifier-3- [nextpnr] gatecat opened issue #287: [interchange] Site pin conflicts in RAM test - https://git.io/J3atP | 13:22 | |
*** citypw has quit IRC | 14:31 | |
*** maartenBE has quit IRC | 15:02 | |
*** maartenBE has joined #symbiflow | 15:04 | |
*** calphool has joined #symbiflow | 15:20 | |
calphool | Hello all, question: how does timing analysis work with the Symbiflow tool chain? | 15:21 |
*** gsmecher has joined #symbiflow | 15:58 | |
Lofty | calphool: As I understand it both VPR and nextpnr output the critical path | 16: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 chip | 16:14 |
sf-slack1 | set. Are those physical characteristics part of what's in the open? | 16:14 |
calphool | Sorry.. I am running both Slack and IRC... calphool = JR | 16:15 |
Lofty | So, uh | 16:18 |
Lofty | Intel stuff comes under Project Mistral, of which I am project lead | 16:18 |
Lofty | It's not technically a Symbiflow project | 16:19 |
Lofty | Anyway, 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 netlist | 16:22 |
Lofty | And if you correlate these with the paths, you now have path timings | 16:23 |
*** calphool has quit IRC | 16:25 | |
umarcor | is 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 |
umarcor | the use case is having multiple designs/bitstreams which all share the same specific BRAM block. | 16:44 |
Lofty | umarcor: https://github.com/YosysHQ/nextpnr/blob/master/docs/constraints.md#absolute-placement-constraints | 16:47 |
umarcor | Lofty: thanks! | 16:48 |
mithro | @acomodi: New prjxray-db push with the new DSP pips - https://github.com/SymbiFlow/prjxray-db/compare/master...mithro:master | 17:27 |
*** rj has joined #symbiflow | 17:27 | |
mithro | gatecat: Need anything from me regarding the interchange format stuff? | 17:31 |
gatecat | mithro: you could give https://github.com/SymbiFlow/python-fpga-interchange/pull/80 a review if you want? otherwise I think all is good | 17:32 |
mithro | calphool - VPR outputs a timing report | 17:32 |
mithro | calphool: VtR also supports timing constraints -> https://docs.verilogtorouting.org/en/latest/vpr/timing_constraints/ | 17:32 |
tpb | Title: Timing Constraints Verilog-to-Routing 8.1.0-dev documentation (at docs.verilogtorouting.org) | 17:33 |
mithro | According 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 |
tpb | Title: Debugging Aids Verilog-to-Routing 8.1.0-dev documentation (at docs.verilogtorouting.org) | 17:33 |
mithro | gatecat: There are a number of BYU students who want to look at graph folding with the interchange format | 17:37 |
gatecat | mithro: excellent | 17:37 |
gatecat | I'm happy to answer questions/discuss ideas if they want | 17:38 |
mithro | gatecat: I've invited Brent (their supervisor) to the interchange format meeting on Thursday morning | 17:38 |
*** rj has quit IRC | 17:50 | |
*** rj has joined #symbiflow | 17:55 | |
*** sorear has quit IRC | 17:58 | |
*** davidlattimore has quit IRC | 17:59 | |
*** _florent_ has quit IRC | 18:01 | |
*** davidlattimore has joined #symbiflow | 18:01 | |
*** sorear has joined #symbiflow | 18:02 | |
*** _florent_ has joined #symbiflow | 18:03 | |
*** rj has quit IRC | 18:34 | |
*** rj has joined #symbiflow | 18:37 | |
*** kgugala_ has joined #symbiflow | 18:57 | |
*** kgugala has quit IRC | 19:00 | |
*** kgugala has joined #symbiflow | 19:10 | |
*** kgugala_ has quit IRC | 19:13 | |
*** kgugala_ has joined #symbiflow | 19:14 | |
*** kgugala has quit IRC | 19:15 | |
*** kgugala has joined #symbiflow | 19:15 | |
*** rj has quit IRC | 19:17 | |
*** kgugala_ has quit IRC | 19:18 | |
*** rj has joined #symbiflow | 19:22 | |
*** kgugala_ has joined #symbiflow | 19:23 | |
*** kgugala__ has joined #symbiflow | 19:26 | |
*** kgugala_ has quit IRC | 19:26 | |
*** kgugala has quit IRC | 19:27 | |
*** kgugala__ has quit IRC | 19:37 | |
*** kgugala has joined #symbiflow | 19:37 | |
*** maartenBE has quit IRC | 19:50 | |
*** maartenBE has joined #symbiflow | 19:56 | |
*** rj has quit IRC | 20:02 | |
*** rj has joined #symbiflow | 20:07 | |
*** rj has quit IRC | 20:46 | |
*** TMM has quit IRC | 20:50 | |
*** TMM has joined #symbiflow | 20:50 | |
*** rj has joined #symbiflow | 20:51 | |
*** rj has quit IRC | 21:29 | |
*** rj has joined #symbiflow | 21:33 | |
*** adjtm has joined #symbiflow | 22:01 | |
*** rj has quit IRC | 22:13 | |
*** rj has joined #symbiflow | 22:19 | |
*** kgugala has quit IRC | 22: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 IRC | 22:59 | |
*** rj has joined #symbiflow | 23: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 environment | 23:28 |
*** rj has quit IRC | 23:38 | |
*** rj has joined #symbiflow | 23: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 IRC | 23:43 | |
*** rj has joined #symbiflow | 23:44 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!