enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
xtro has quit [Ping timeout: 240 seconds]
OmniMancer1 has joined #symbiflow
OmniMancer has quit [Ping timeout: 256 seconds]
proteus-guy has quit [Ping timeout: 256 seconds]
OmniMancer has joined #symbiflow
OmniMancer1 has quit [Ping timeout: 260 seconds]
enriq has joined #symbiflow
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
catphish has quit [Remote host closed the connection]
kraiskil has joined #symbiflow
kraiskil has quit [Ping timeout: 260 seconds]
enriq has joined #symbiflow
enriq has quit [Client Quit]
enriq has joined #symbiflow
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
craigo has quit [Ping timeout: 256 seconds]
enriq has joined #symbiflow
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
enriq has joined #symbiflow
craigo has joined #symbiflow
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
kraiskil has joined #symbiflow
kraiskil has quit [Ping timeout: 240 seconds]
kraiskil has joined #symbiflow
skydive has joined #symbiflow
kraiskil has quit [Ping timeout: 260 seconds]
enriq has joined #symbiflow
enriq has quit [Client Quit]
alexhw has quit [Remote host closed the connection]
alexhw has joined #symbiflow
enriq has joined #symbiflow
proteus-guy has joined #symbiflow
maartenBE has quit [Ping timeout: 260 seconds]
maartenBE has joined #symbiflow
<litghost>
skydive: I'm tracking an OOM failure that occurs on arty100T with some placement seeds. We have been seeing it on CI with some frequency. I believe I know how to fix the issue, and will be working on it this week.
<skydive>
Thanks a lot for the update!
kraiskil has joined #symbiflow
<litghost>
skydive: So as a workaround, you can provide another seed to the placement step, and it "typically" works. To pass a seed to placement set env var VPR_SEED="--seed <int>" before invoking the flow
<litghost>
skydive: Not ideal, but might give you a chance to make progress while we work on a fix
<litghost>
skydive: It is worth noting that I expect the arty100T flow right now to use ~2-6 GB. It is worth noting that not all of that is resident at the same time, but it does imply a minimum RAM requirement for the moment
<skydive>
litghost: thanks for the heads up regarding RAM. I should be fine, I have about 7GB free.
<skydive>
Setting that environment variable seems to break the symbiflow_pack command. "vpr architecture circuit" is telling me --seed is an unexpected argument.
<litghost>
skydive: Huh, let me check, I might have provide a bad argument then
<skydive>
Whoops - i accidently had an equals in there.
<litghost>
skydive: Ya, that'll do it
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #symbiflow
<sf-slack>
<ryancj14> @mithro: I've studied fpga-tool-perf extensively now and I was wondering if it might be nice to have a wiki for fpga-tool-perf. I've compiled some of the notes I've taken on the repo into an example wiki in ryancj14/fpga-tool-perf: https://github.com/ryancj14/fpga-tool-perf/wiki Do you think something like this would be a good addition to the repo?
<tpb>
Title: Home · ryancj14/fpga-tool-perf Wiki · GitHub (at github.com)
skydive has quit [Ping timeout: 240 seconds]
skydive has joined #symbiflow
<mithro>
ryancj14: Yes
OmniMancer has quit [Quit: Leaving.]
<_whitenotifier-b>
[fpga-tool-perf] ryancj14 opened issue #189: Adding wiki to fpga-tool-perf - https://git.io/JJ0Ah
xtro has joined #symbiflow
<skydive>
litghost: Even after exporting the seed, it still doesn't seem to work reliably. Same problem. Do you have an example seed that functions properly?
<skydive>
I'll be patient - thanks for working on this!
<litghost>
skydive: Huh, can you file an issue and attach the failing log file?
<skydive>
Will do so tonight. What's the optimal way to get a log output? (Command) > file.log 2>&1
<litghost>
skydive: Logs should be in files with extension *.log, so simply tar them all
citypw has quit [Ping timeout: 240 seconds]
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
enriq has joined #symbiflow
<sf-slack>
<johnnybui> Is there any specific reason that the icebreaker board is reporting frequency as 81.05 while all the other boards/toolchains have frequencies in the millions (246366100). I assume it's some issue with inconsistency with units (hertz vs megahertz). Here's an example: https://gist.github.com/TypingKoala/80a1144e30eb3d678f30f8f063baea63
<litghost>
johnnybui: Seems like a bug? Please file an issue with the relevant info so it can be cleaned up, both in the code and in the documentation
hzeller has joined #symbiflow
<_whitenotifier-b>
[fpga-tool-perf] TypingKoala opened issue #190: Inconsistent units for icebreaker board max frequency - https://git.io/JJEJK
<_whitenotifier-b>
[FPGA-Tool-Performance-Visualization-Library] TypingKoala opened issue #11: Implement enums for AddNormalizedColumn direction parameter - https://git.io/JJETW
enriq has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<tpb>
Title: GitHub - SymbiFlow/symbiflow-xc7z-automatic-tester: Tool for automatically testing FPGA designs using a Zynq Series 7 board. (at github.com)