| *** tpb <[email protected]> has joined #f4pga | 00:00 | |
| *** JTL is now known as JiTtLe | 00:04 | |
| *** JiTtLe is now known as JTL | 00:52 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Ping timeout: 268 seconds) | 02:56 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 03:29 | |
| *** scientes <[email protected]> has joined #f4pga | 04:33 | |
| *** scientes <[email protected]> has quit IRC (Ping timeout: 252 seconds) | 04:59 | |
| *** rvalles <rvalles!~rvalles@user/rvalles> has quit IRC (Ping timeout: 260 seconds) | 05:20 | |
| *** rvalles <rvalles!~rvalles@user/rvalles> has joined #f4pga | 05:31 | |
| *** rvalles <rvalles!~rvalles@user/rvalles> has quit IRC (Ping timeout: 240 seconds) | 05:37 | |
| *** rvalles <rvalles!~rvalles@user/rvalles> has joined #f4pga | 05:50 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga | 06:34 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 07:12 | |
| *** TMM_ <[email protected]> has joined #f4pga | 07:12 | |
| *** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Quit: ec) | 08:08 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Remote host closed the connection) | 08:12 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 08:13 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Remote host closed the connection) | 08:48 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 08:50 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Remote host closed the connection) | 12:01 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 12:03 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Ping timeout: 268 seconds) | 12:18 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 12:19 | |
| *** jacobk <[email protected]> has joined #f4pga | 15:33 | |
| *** jacobk <[email protected]> has quit IRC (Ping timeout: 255 seconds) | 16:19 | |
| *** jacobk <[email protected]> has joined #f4pga | 16:21 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Ping timeout: 268 seconds) | 16:54 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 16:56 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 17:02 | |
| *** TMM_ <[email protected]> has joined #f4pga | 17:02 | |
| F4PGASlackBridge | <afranklint16> Does anyone else have experience targeting eos-s3 architecture in f4pga? I'm getting an error where yosys says it can't find the `ql-qlf` module from the plugins directory. Am I missing something? | 18:01 |
|---|---|---|
| F4PGASlackBridge | <kgugala> hmm in CI the plugin is built and passes the tests https://github.com/chipsalliance/yosys-f4pga-plugins/runs/7299097151?check_suite_focus=true#step:8:99 | 18:05 |
| F4PGASlackBridge | <kgugala> which GCC version do you use? | 18:06 |
| F4PGASlackBridge | <afranklint16> My system GCC is 9.4 and I assume that's what yosys is using | 18:07 |
| F4PGASlackBridge | <afranklint16> I have tried building the yosys plugins from the repo but I ran into this problem | 18:09 |
| F4PGASlackBridge | <kgugala> do you build it against yosys installed in your system? | 18:11 |
| F4PGASlackBridge | <kgugala> or did you build yosys from scratch? | 18:12 |
| F4PGASlackBridge | <afranklint16> I tried both and the same thing happened although it's possible that it still used the default yosys that came with the f4pga eos-s3 install | 18:12 |
| F4PGASlackBridge | <kgugala> so plugins build will use complier reported by `yosys-config --cxx` | 18:14 |
| F4PGASlackBridge | <kgugala> what do you get from this command? | 18:14 |
| F4PGASlackBridge | <afranklint16> `x86_64-conda_cos6-linux-gnu-gcc` | 18:15 |
| F4PGASlackBridge | <kgugala> and `x86_64-conda_cos6-linux-gnu-gcc --version`? | 18:15 |
| F4PGASlackBridge | <afranklint16> it just says command not found | 18:16 |
| F4PGASlackBridge | <kgugala> do you manually set the `CXX` env ? | 18:17 |
| F4PGASlackBridge | <kgugala> and what do you get from `yosys-config --cxxflags`? | 18:17 |
| F4PGASlackBridge | <afranklint16> I have not tried setting the CXX variable | 18:17 |
| F4PGASlackBridge | <afranklint16> my flags look like this | 18:22 |
| F4PGASlackBridge | <afranklint16> ```-fvisibility-inlines-hidden -std=c++17 -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem ~/opt/f4pga/eos-s3/conda/envs/eos-s3/include -fdebug-prefix-map=/home/runner/work/conda-eda/conda-eda/workdir/conda-env/conda-bld/quicklogic-yosys_1625138793175/work=/usr/local/src/conda/quicklogic-yosys-0.8.0_105_gd282be04 | 18:22 |
| F4PGASlackBridge | -fdebug-prefix-map=~/opt/f4pga/eos-s3/conda/envs/eos-s3=/usr/local/src/conda-prefix -Wall -Wextra -ggdb -I~/opt/f4pga/eos-s3/conda/envs/eos-s3/share/yosys/include -MD -D_YOSYS_ -fPIC -I~/opt/f4pga/eos-s3/conda/envs/eos-s3/include -std=c++11 -Os -I~/opt/f4pga/eos-s3/conda/envs/eos-s3/include -DYOSYS_ENABLE_PLUGINS -DYOSYS_ENABLE_GLOB -DYOSYS_ENABLE_ZLIB -I~/opt/f4pga/eos-s3/conda/envs/eos-s3/include -DYOSYS_ENABLE_TCL | 18:22 |
| F4PGASlackBridge | -DYOSYS_ENABLE_ABC -DYOSYS_ENABLE_COVER``` | 18:22 |
| F4PGASlackBridge | <kgugala> my guess is that you have too old yosys in your env (in conda) | 18:23 |
| F4PGASlackBridge | <afranklint16> Interesting, as I installed the f4pga eos-s3 environment just this week | 18:24 |
| F4PGASlackBridge | <afranklint16> Would it be using the same version of yosys as the xc7 f4pga install? | 18:24 |
| F4PGASlackBridge | <afranklint16> I appreciate the help by the way | 18:25 |
| F4PGASlackBridge | <kgugala> the CI in plugins use https://github.com/chipsalliance/yosys-f4pga-plugins/blob/main/environment.yml#L22 | 18:26 |
| F4PGASlackBridge | <afranklint16> This is what I get when I run yosys --version | 18:30 |
| F4PGASlackBridge | <afranklint16> ```Yosys 0.9+2406 (git sha1 d282be04, x86_64-conda_cos6-linux-gnu-gcc 1.24.0.133_b0863d8_dirty -fvisibility-inlines-hidden -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections | 18:31 |
| F4PGASlackBridge | -fdebug-prefix-map=/home/runner/work/conda-eda/conda-eda/workdir/conda-env/conda-bld/quicklogic-yosys_1625138793175/work=/usr/local/src/conda/quicklogic-yosys-0.8.0_105_gd282be04 -fdebug-prefix-map=~/opt/f4pga/eos-s3/conda/envs/eos-s3=/usr/local/src/conda-prefix -fPIC -Os)``` | 18:31 |
| F4PGASlackBridge | <afranklint16> so maybe I am out of date | 18:31 |
| F4PGASlackBridge | <afranklint16> Okay it looks like when I rebuilt yosys from source it didn't install it in the environment, so I left the environment and now it's advancing past the point I was stuck on | 18:35 |
| F4PGASlackBridge | <kgugala> yosys in your env is 0.8, while the one used in plugins is 0.17 (way newer) | 18:35 |
| F4PGASlackBridge | <afranklint16> Yes, I see that now. I didn't realize that building yosys wouldn't replace the environment yosys | 18:37 |
| F4PGASlackBridge | <kgugala> what do you try to do? | 18:37 |
| F4PGASlackBridge | <kgugala> maybe you can deactivate conda env and build everything using native env? | 18:38 |
| F4PGASlackBridge | <afranklint16> yes that's what I'm doing | 18:38 |
| F4PGASlackBridge | <afranklint16> it says it can't find uhdm.h | 18:38 |
| F4PGASlackBridge | <afranklint16> I think I need to build the yosys uhdm plugin integration repo? | 18:38 |
| F4PGASlackBridge | <kgugala> or build uhdm natively | 18:38 |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has quit IRC (Remote host closed the connection) | 19:45 | |
| *** chexum <chexum!~quassel@gateway/tor-sasl/chexum> has joined #f4pga | 19:45 | |
| *** jacobk <[email protected]> has quit IRC (Ping timeout: 244 seconds) | 21:47 | |
| *** jacobk <[email protected]> has joined #f4pga | 21:55 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!