Saturday, 2021-03-20

*** tpb has joined #symbiflow00:00
sf-slack<timo.callahan> I'm seeing this when trying to use Symbiflow for a LiteX build.   I don't know what changed; it worked three weeks ago, and I don't think I've updated Symbiflow or LiteX.  `ERROR: set_property IO_LOC_PAIRS: Incorrect number of arguments.`   I'm using symbiflow from a symbiflow-examples install that I did in December.   Where should I start looking?01:03
litghostDid you update the symbiflow plugins?01:14
sf-slack<timo.callahan> Where do they live?   How could I have accidentally updated them?    Or are you suggesting that I *should* update them?01:26
litghostI guess the question I have is what changed.  Have you updated any packages?01:30
litghostThe latest set of packages clearly work, but how is your system different from that01:30
sf-slack<timo.callahan> Do you think the issue is strictly in SymbiFlow, or potentially with LiteX?   Actually let me check myself by running some of the examples in symbiflow-examples....01:33
litghostIO_LOC_PAIRS is symbiflow specific01:34
litghostSo I can confidently say it's something in SymbiFlow01:34
litghostBut maybe not01:34
litghostIf for some reason LiteX set a pindef to "" (e.g. empty) that could mess things up01:34
litghostFor example, "set_property IO_LOC_PAIRS X5 [get_cells X]" is legal, but "set_property IO_LOC_PAIRS [get_cells X]" would not be01:35
litghostAnother possibility is that you have a mismatch between packages, and rather than generating a nice message, it generates that message (e.g. a bug)01:35
sf-slack<timo.callahan> Hmm, symbiflow examples are working for me (counter, picosoc_demo), so let me try to find a different LiteX directory to try rebuilding.   Thanks for your help, @litghost!01:47
*** hansfbaier has quit IRC02:02
sf-slack<timo.callahan> More info: Symbiflow stil does work with the older LiteX build I had.   But I still see the error with my new build.   Also, I see a warning right before the error:   `Warning: Couldn't find port matching serial_tx` then `ERROR: set_property IO_LOC_PAIRS: Incorrect number of arguments.`.   But `serial_tx` does exist; it's an output reg on the top "arty" module.   And if I comment out the lines regarding02:40
sf-slack`serial_tx` in arty.xdc, then I see the warning with the next pin (`serial_rx`), and then the error.02:40
*** Degi has quit IRC02:42
*** Degi has joined #symbiflow02:45
sf-slack<timo.callahan> Ok, I think the problem is that "symbiflow_synth" is not finding the right top, even though we specify "-t arty".02:51
*** _whitelogger_ has joined #symbiflow03:44
*** shah has joined #symbiflow03:58
*** shah has quit IRC04:02
*** krogozinski_ has quit IRC04:24
sf-slack<timo.callahan> More findings: my custom function unit module Verilog, which was generated from nmigen/yosys, was marked `(* top = 1 *)`, but was then included into VexRiscv, which was then included into Litex (`arty`).   Because of the attribute, the custom function unit module became the top when everything was fed into `symbiflow_synth` / yosys, and all other modules (Litex, VexRiscv)  were removed.   Which then led to the04:29
sf-slackobscure error, because those top LiteX pins had been trimmed.   Debugging was made more difficult initially by the fact that info and warnings from synthesis were sent to /dev/null by the Makefile recipe.04:29
*** krogozinski has joined #symbiflow04:38
tcalNew error!05:07
tcalhttps://www.irccloud.com/pastebin/YGpTLHUf/05:08
tpbTitle: Snippet | IRCCloud (at www.irccloud.com)05:08
tcalSomeone else encountered the same thing I know, since I found their pastebin :)05:08
*** _whitelogger_ has quit IRC06:09
*** _whitelogger_ has joined #symbiflow06:11
*** kraiskil has joined #symbiflow06:23
*** _whitelogger_ has quit IRC06:33
*** _whitelogger_ has joined #symbiflow06:35
*** _whitelogger_ has quit IRC06:45
*** _whitelogger_ has joined #symbiflow06:47
*** kgugala_ has joined #symbiflow06:53
*** kgugala has quit IRC06:55
*** kgugala_ has quit IRC06:57
*** kgugala has joined #symbiflow06:57
*** _whitelogger_ has quit IRC07:03
*** _whitelogger_ has joined #symbiflow07:05
*** kraiskil has quit IRC07:12
*** kraiskil has joined #symbiflow08:03
*** tannewt has quit IRC08:09
*** tannewt has joined #symbiflow08:10
*** tannewt has quit IRC08:10
*** tannewt has joined #symbiflow08:10
*** kgugala has quit IRC08:11
*** kgugala has joined #symbiflow08:11
*** kraiskil has quit IRC09:07
*** hansfbaier has joined #symbiflow09:24
*** FLOKLI is now known as flokli09:42
*** kraiskil has joined #symbiflow10:22
*** hansfbaier has quit IRC10:48
*** kraiskil has quit IRC12:55
*** kraiskil has joined #symbiflow13:01
*** kraiskil has quit IRC13:11
*** kraiskil has joined #symbiflow14:00
*** craigo has joined #symbiflow14:07
*** TMM has quit IRC14:17
*** TMM has joined #symbiflow14:17
*** kraiskil has quit IRC14:46
*** craigo has quit IRC15:35
*** kraiskil has joined #symbiflow16:06
*** epony has quit IRC16:18
*** epony has joined #symbiflow16:22
*** craigo has joined #symbiflow18:28
*** epony has quit IRC19:16
*** epony has joined #symbiflow19:17
*** krogozinski has quit IRC21:33
*** kraiskil has quit IRC21:52
*** krogozinski has joined #symbiflow21:55
*** xtro has joined #symbiflow22:39
*** xtro is now known as Guest7155822:39
*** Guest71558 has left #symbiflow22:42
mithrolitghost / acomodi: https://github.com/SymbiFlow/prjxray-db/compare/master...mithro:master22:44
-_whitenotifier-4- [symbiflow-examples] tcal-x opened issue #131: check_if_rest_of_carry4_is_unused: assert cell_idx < len(O_ports) - 1 - https://git.io/JmHuZ23:42

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