futarisIRCcloud has quit [Quit: Connection closed for inactivity]
TMM has quit [Ping timeout: 240 seconds]
TMM has joined #symbiflow
maartenBE has quit [Ping timeout: 256 seconds]
maartenBE has joined #symbiflow
krogozinski_ has joined #symbiflow
krogozinski has quit [Ping timeout: 240 seconds]
sorear has quit [Ping timeout: 265 seconds]
davidlattimore has quit [Ping timeout: 265 seconds]
sorear has joined #symbiflow
jopdorp has quit [Ping timeout: 265 seconds]
davidlattimore has joined #symbiflow
jopdorp has joined #symbiflow
Niklas[m] has quit [*.net *.split]
gruetzkopf has quit [*.net *.split]
flokli has quit [*.net *.split]
Niklas[m] has joined #symbiflow
gruetzkopf has joined #symbiflow
flokli has joined #symbiflow
unrznbl[m] has quit [Ping timeout: 240 seconds]
Niklas[m] has quit [Ping timeout: 240 seconds]
abeljj[m] has quit [Ping timeout: 244 seconds]
xobs has quit [Ping timeout: 240 seconds]
promach3 has quit [Ping timeout: 268 seconds]
unrznbl[m] has joined #symbiflow
futarisIRCcloud has joined #symbiflow
xobs has joined #symbiflow
Niklas[m] has joined #symbiflow
abeljj[m] has joined #symbiflow
citypw_ has joined #symbiflow
Niklas[m] has quit [Ping timeout: 258 seconds]
unrznbl[m] has quit [Ping timeout: 260 seconds]
xobs has quit [Ping timeout: 265 seconds]
abeljj[m] has quit [Ping timeout: 260 seconds]
citypw_ has quit [Quit: Leaving]
hansfbaier has joined #symbiflow
xobs has joined #symbiflow
promach3 has joined #symbiflow
Niklas[m] has joined #symbiflow
bjorkintosh has joined #symbiflow
unrznbl[m] has joined #symbiflow
abeljj[m] has joined #symbiflow
cr1901_modern1 has joined #symbiflow
HackerFoo1 has joined #symbiflow
TMM has quit [*.net *.split]
rvalles has quit [*.net *.split]
HackerFoo has quit [*.net *.split]
cr1901_modern has quit [*.net *.split]
Lofty has quit [*.net *.split]
ssb has quit [*.net *.split]
cr1901_modern1 has quit [Quit: Leaving.]
cr1901_modern has joined #symbiflow
Niklas[m] has quit [Ping timeout: 246 seconds]
unrznbl[m] has quit [Ping timeout: 265 seconds]
Degi has quit [Ping timeout: 264 seconds]
Degi has joined #symbiflow
hosana has quit [Ping timeout: 246 seconds]
Lofty has joined #symbiflow
ssb has joined #symbiflow
TMM has joined #symbiflow
TMM has quit [Max SendQ exceeded]
Niklas[m] has joined #symbiflow
TMM has joined #symbiflow
hosana has joined #symbiflow
rvalles has joined #symbiflow
unrznbl[m] has joined #symbiflow
<sf-slack>
<jgoeders> @litghost Thanks. "make install" with capnproto-java did the trick. Now I'm running into: ```AttributeError: capnp/schema.c++:493: failed: struct has no such member; name = name``` I'm guessing my RapidWright version is somehow out of sync with something. I'll check into it later. Also, I tried setting up fasm2bels on my office computer today, but ran into the same `Could not find a version that satisfies the
<sf-slack>
requirement rapidyaml (from python-fpga-interchange)` issue mentioned above. Is there a fix for that? Thanks!
cr1901_modern has quit [Read error: Connection reset by peer]
cr1901_modern has joined #symbiflow
smkz has quit [Quit: smkz]
smkz has joined #symbiflow
craigo has joined #symbiflow
hansfbaier1 has joined #symbiflow
hansfbaier has quit [Ping timeout: 240 seconds]
<lambda>
symbiflow_pack fails with "Failed to find matching architecture model for 'PLLE2_BASE'", is that just not supported and I have to use PLLE2_ADV instead?
<sf-slack>
<kgugala> @acomodi @mkurc^^
<lambda>
hm, it's in the techmap, guess yosys just didn't pick up on it for whatever reason?
<sf-slack>
<acomodi> At the moment the architecture does not include the PLLE2_BASE. I think it still needs to be added. PLLE2_ADV is supported though
<sf-slack>
<mkurc> PLLE2_ADV works for sure. If PLLE2_BASE didn't work then probably the techmap in SymbiFlow is incorrect. It should map BASE to ADV in the same way as Vivado does.
<lambda>
alright, I just expected yosys to a PLLE2_ADV and subsequently a PLLE2_ADV_VPR, that's what cells_map.v says
<lambda>
*to map it to a
<lambda>
ah yeah, there are mismatches in the PLLE2_BASE I/Os between yosys' cells_xtra.v and arch-defs' cells_map.v
<sf-slack>
<mkurc> @lambda Could you file an issue about that on SymbiFlow/symbiflow-arch-defs Github repo so that we won't forget about the mismatch?
<lambda>
will do
<sf-slack>
<mkurc> thanks
hansfbaier1 has quit [Read error: Connection reset by peer]
<_whitenotifier>
[symbiflow-arch-defs] Xiretza opened issue #1991: PLLE2_BASE techmap doesn't match yosys' cells - https://git.io/Jt83Q
<lambda>
I'm currently trying to get my design to build using only the symbiflow tools (used nextpnr-xilinx previously), so I may have a few more questions and issues in the next few days ;)
<lambda>
like just now where symbiflow_route fails to route a clock from a PLL to... somewhere (`BLK-TL-CMT_TOP_L_UPPER_T[0].CMT_TOP_R_UPPER_T_PLLE2_CLKOUT3[0]` to `BLK-TL-CLBLL_L[0].CLBLL_L_CLK[0]`) - are there any known issues with clock routing?
<sf-slack>
<acomodi> This might has to do with the fact that global clock buffers auto-inference is disabled. There needs to be an explicit BUFG connected to the clk output of the PLL instantiated at the moment
<lambda>
ah, that makes, sense thanks
<nickoe>
litghost: Anything we can do to satisfy the ci?
FFY00 has quit [*.net *.split]
lopsided98 has quit [*.net *.split]
xobs has quit [*.net *.split]
sorear has quit [*.net *.split]
yeti has quit [*.net *.split]
lopsided98 has joined #symbiflow
FFY00 has joined #symbiflow
lopsided98 has quit [Max SendQ exceeded]
xobs has joined #symbiflow
yeti has joined #symbiflow
sorear has joined #symbiflow
lopsided98 has joined #symbiflow
futarisIRCcloud has quit [*.net *.split]
LoneTech has quit [*.net *.split]
futarisIRCcloud has joined #symbiflow
LoneTech has joined #symbiflow
abeljj[m] has quit [Ping timeout: 268 seconds]
futarisIRCcloud has quit [Max SendQ exceeded]
Niklas[m] has quit [Ping timeout: 264 seconds]
futarisIRCcloud has joined #symbiflow
xobs has quit [Ping timeout: 265 seconds]
infinite_recursi has joined #symbiflow
promach3 has quit [Ping timeout: 240 seconds]
lopsided98 has quit [Ping timeout: 264 seconds]
unrznbl[m] has quit [Ping timeout: 272 seconds]
lopsided98 has joined #symbiflow
FFY00 has quit [Ping timeout: 244 seconds]
abeljj[m] has joined #symbiflow
Niklas[m] has joined #symbiflow
unrznbl[m] has joined #symbiflow
xobs has joined #symbiflow
abeljj[m] has quit [Ping timeout: 260 seconds]
xobs has quit [Ping timeout: 268 seconds]
unrznbl[m] has quit [Ping timeout: 240 seconds]
Niklas[m] has quit [Ping timeout: 268 seconds]
FFY00 has joined #symbiflow
promach3 has joined #symbiflow
<lambda>
acomodi: it builds now with BUFGs on all the PLL outputs, just doesn't work - looking forward to some incredibly fun debugging
<sf-slack>
<acomodi> lmabda: you mean doesn't work on HW?
<lambda>
acomodi: yeah, there aren't really any life signs - will have to investigate and employ some debug LEDs
<sf-slack>
<acomodi> lambda: All right. One thing to check would be timing violations, and, if they exists, how bad they are. Just to be sure, have you applied time constraints in the XDC (or SDC)?
<lambda>
acomodi: I have a create_clock for all my PLL inputs and outputs, though I think the outputs may actually be induced automatically with this flow?
<lambda>
at least if `propagate_clocks` in synth.tcl does what I think it does
<lambda>
iirc routing failed setup timing massively, I assumed that was just a glitch since (1) timing reports with nextpnr were always pretty sketchy and (2) the counter example also failed in a similar fashion
<sf-slack>
<acomodi> Well, you can check if the propagate_clocks did something if, in the build directory you got an <design>.sdc file. That should include all propagated clock constraints for VPR
<sf-slack>
<acomodi> Also, you can check if timing constraints got correctly applied if the `route.log` log file contains a string such as `Applied <N> SDC commands from <SDC file name>`
<lambda>
no, doesn't seem like clocks are actually propagated over PLLs, I'll just continue defining them manually
<sf-slack>
<acomodi> Ok, there is also another thing to do which is add a clock constraint in the XDC to the top level clock port (if you get the clock from there)
<sf-slack>
<acomodi> Sth like `create_clock -period <period> <input_clock_port>`
<lambda>
that port is only used as my PLL input and I have a create_clock on that
<lambda>
-50000ns sTNS and -20ns sWNS sure would break about everything if those numbers are to be believed ;)
<lambda>
oops, my bad, I'm actually using the input clock for logic that's shared with the core clock - no surprise that doesn't work
citypw has quit [Ping timeout: 268 seconds]
<lambda>
can vtr show the critical path? I don't think these two clocks share any logic anymore, but they still show up as a huge sWNS after placement
<sf-slack>
<acomodi> I am not sure if this is by default, but VTR can emit a detailed report with the worst paths (report_timing.setup.rpt)
<litghost>
I believe the reports are generated by default
<litghost>
I believe it prints the 100 highest critical path, both setup and hold
<lambda>
symbiflow_place isn't showing it, I'll look into that option
<sf-slack>
<arvindsrinivasan> Hello! So I’m attempting to install symbiflow from source per this page (https://symbiflow.readthedocs.io/en/latest/symbiflow-arch-defs/docs/source/getting-started.html) and it seems the `make env` stage is failing due to conda not being able to find these packages: ``` - litex-hub::gcc-riscv64-elf-newlib==9.2.0=20201119_154229 - litex-hub::zachjs-sv2v==0.0.5_0025_ge9f9696=20201120_205532 -
<sf-slack>
litex-hub::vtr-optimized==v8.0.0_3049_g64d15e2dd=20201217_025303 - litex-hub::capnproto-java==0.1.5_0012_g44a8c1e=20201104_165332 - litex-hub::prjxray-tools==0.1_2697_g0f939808=20201120_145821 - litex-hub::prjxray-db==v0.0_243_g057e179=20210119_091808``` Is this to be expected or is there further configuration that would be necessary. On MacOS 10.14.6 doing a clean install.
<tpb>
Title: Getting Started SymbiFlow (at symbiflow.readthedocs.io)
<sf-slack>
<acomodi> Oh, I mis-read. I don't think that after placement you have this information, you would need to wait for routing
<litghost>
nickoe: I missing something in my fixed yesterday, I'll fix it today
SmutLord^ has quit [Remote host closed the connection]
<lambda>
litghost: got it semi-working! still failing timing and something is wrong with interrupts, but that may just be because of the former
SmutLord^ has joined #symbiflow
<litghost>
lambda: Almost certainly
<sf-slack>
<arvindsrinivasan> Alright, now I have further questions on the install process on Ubuntu 20.10. I’m getting an error at in the install process regarding the rapidyaml package. I can’t seem to find the package on pypi, so has its name changed?
<litghost>
Pull latest version
<litghost>
Should be fixed
<nickoe>
litghost: cool :)
FFY00 has quit [Read error: Connection reset by peer]
ym_ has quit [Quit: Leaving]
FFY00 has joined #symbiflow
<sf-slack>
<arvindsrinivasan> Alright @litghost sorry to bother again, but now I’m getting a error building a wheel for rapidyaml since it uses PEP 517 and can’t be installed directly?
<litghost>
Error?
<sf-slack>
<arvindsrinivasan> Copy paste is being weird so image
nickoe has quit [Ping timeout: 246 seconds]
kgugala has joined #symbiflow
kgugala__ has quit [Ping timeout: 260 seconds]
<sf-slack>
<arvindsrinivasan> @litghost
<litghost>
What? You didn't paste anything?
<sf-slack>
<mgielda> its visible on slack
<sf-slack>
<mgielda> maybe not on IRC though
<sf-slack>
<mgielda> perhaps pastebin or similar will work @arvindsrinivasan
<litghost>
Nothing on IRC
<litghost>
Anyways
<litghost>
arvindsrinivasan: The error is that the build failed
<litghost>
You need to keep scrolling up
<litghost>
You copied the wrong error
<litghost>
The error above say "Failed to build wheel", and then the log above that is why the wheel failed to build