00:38 <umarcor|2> mithro, CarlosEDP, if you mean the ghdl-yosys-plugin, there are two different approaches.

00:38 <umarcor|2> on windows (MSYS2) the plugin is built into yosys, because yosys does not support dynamically loading modules on windows (yet)

00:39 <umarcor|2> on linux (containers) the plugin is built as a shared library (module) and shipped "independently".

00:39 <umarcor|2> however, the plugin does always depend on a working GHDL installation. no matter if it's built-in or a module.

00:40 <umarcor|2> that's because the plugin using libghdl, which uses the standard and IEEE libraries in the GHDL installation.

00:40 <umarcor|2> so, the plugin does not use the GHDL binary, but it uses almost all the rest of the content of an installation.

00:40 <umarcor|2> that's why GHDL is a dependency of Yosys on MSYS2

06:42 <sf-slack> <kgugala> test test ...

06:42 <sf-slack> <kgugala> @mithro the bridge is back

10:01 <_whitenotifier-3> [fpga-interchange-schema] gatecat opened issue #47: Site PIPs with side effects - https://git.io/J3JaC

12:27 <CarlosEDP> umarcor|2: Also the XDC plugin I got a PR merged... it added -dict support for constraints.

16:08 <mithro> acomodi: You wanted me to setup kokoro for something right?

16:09 <sf-slack> <acomodi> mithro: yep, should be setup here: https://github.com/SymbiFlow/fpga-interchange-tests

16:09 <mithro> @acomodi If you don't keep poking me it will never happen :-)

16:11 <sf-slack> <acomodi> yeah, I guess I'll increase the poking frequency then :)

16:12 <sf-slack> <acomodi> There is a PR that adds a basic kokoro configuration here: https://github.com/SymbiFlow/fpga-interchange-tests/pull/4

16:13 <mithro> We only need ubuntu testing right?

16:14 <sf-slack> <acomodi> Yeah, I think it is enough

16:14 <sf-slack> <acomodi> Probably we can have other OSes and distros testing setup with GH actions instead

17:04 <jhu> [13:13:43] <jhu> Hi guys, Im trying to build the linux-on-litex project with symbiflow toolchain and seems like im running into this error each time.... does anything know what's going on?

17:04 <jhu> [13:13:56] <jhu> ake: Leaving directory '/home/jhu96/Desktop/McGill_Masters/Research/linux-on-litex-vexriscv/build/digilent_arty/software/bios'

17:04 <jhu> [13:13:56] <jhu> INFO:SoC:Initializing ROM rom with contents (Size: 0x9ed0).

17:04 <jhu> [13:13:56] <jhu> INFO:SoC:Auto-Resizing ROM rom from 0x10000 to 0x9ed0.

17:04 <jhu> [13:13:56] <jhu> symbiflow_synth -t digilent_arty -v /home/jhu96/Desktop/McGill_Masters/Research/litex/pythondata-cpu-vexriscv-smp/pythondata_cpu_vexriscv_smp/verilog/Ram_1w_1rs_Generic.v

17:04 <jhu> /home/jhu96/Desktop/McGill_Masters/Research/litex/pythondata-cpu-vexriscv-smp/pythondata_cpu_vexriscv_smp/verilog/VexRiscvLitexSmpCluster_Cc2_Iw64Is8192Iy2_Dw64Ds8192Dy2_Ldw128_Cdma_Ood_Rvc.v /home/jhu96/Desktop/McGill_Masters/Research/linux-on-litex-vexriscv/build/digilent_arty/gateware/digilent_arty.v -d artix7 -p xc7a35tcsg324-1 -x

17:04 <jhu> digilent_arty.xdc > /dev/null

17:04 <jhu> [13:13:56] <jhu> ERROR: Cell $iopadmap$digilent_arty.sdcard_cd of type \IBUF doesn't support the \SLEW attribute

17:04 <jhu> [13:13:56] <jhu> make: *** [Makefile:34: digilent_arty.eblif] Error 1

17:04 <jhu> [13:13:56] <jhu> Traceback (most recent call last):

17:04 <jhu> [13:13:56] <jhu>   File "./make.py", line 634, in <module>

17:04 <jhu> [13:13:56] <jhu>     main()

17:04 <jhu> [13:13:56] <jhu>   File "./make.py", line 615, in main

17:04 <jhu> [13:13:56] <jhu>     builder.build(run=args.build)

17:04 <jhu> [13:13:56] <jhu>   File "/home/jhu96/Desktop/McGill_Masters/Research/litex/litex/litex/soc/integration/builder.py", line 281, in build

17:04 <jhu> [13:13:56] <jhu>     vns = self.soc.build(build_dir=self.gateware_dir, **kwargs)

17:04 <jhu> [13:13:56] <jhu>   File "/home/jhu96/Desktop/McGill_Masters/Research/litex/litex/litex/soc/integration/soc.py", line 1098, in build

17:04 <jhu> [13:13:56] <jhu>     return self.platform.build(self, *args, **kwargs)

17:06 <jhu> Hi guys,  I previously asked this question in #litex but they told me to come to you guys. I don't really understand what the error means when I'm trying to create the bitstream with the symbiflow toolchain. Is there something wrong with how i configured the installation of symbiflow?

17:42 <sf-slack1> <acomodi> jhu: It might be that there is something wrong with the XDC, or indeed the symbiflow setup. I suggest to open an issue in symbiflow-examples (https://github.com/SymbiFlow/symbiflow-examples) with a description of the error and the steps required to reproduce it

17:52 <jhu> Ok thanks!

17:56 <jhu> Do you have any suggestions on how i could fix this problem? I will post an issue on there as well.

17:58 <mithro> jhu: I think we need the github issue with the full details to diagnose the problem

18:08 <_whitenotifier-3> [symbiflow-examples] jhu960213 opened issue #143: Symbiflow build error when using "Linux-on-litex-vexriscv" project from Enjoy Digital - https://git.io/J3kJF

18:11 <jhu> sf-slack1 mithro I just opened the issue