<mithro>
tim.callahan: Take the design back into Vivado and see if there are any timing violations
<sf-slack>
<timo.callahan> will do
citypw has joined #symbiflow
citypw has quit [Remote host closed the connection]
citypw has joined #symbiflow
citypw has quit [Ping timeout: 240 seconds]
proteus-guy has quit [Ping timeout: 246 seconds]
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #symbiflow
<sf-slack>
<timo.callahan> mithro: I should have said "will try" -- I haven't figured it out yet. If it's complicated (as in using partial reconfig), we can talk about it tomorrow. Or did I just not find the right menu in vivado?
Bertl_oO is now known as Bertl_zZ
OmniMancer1 has joined #symbiflow
OmniMancer has quit [Ping timeout: 256 seconds]
citypw has joined #symbiflow
az0re has quit [Remote host closed the connection]
wavedrom has quit [Ping timeout: 256 seconds]
adjtm_ has joined #symbiflow
adjtm has quit [Ping timeout: 256 seconds]
proteusguy has quit [Remote host closed the connection]
proteusguy has joined #symbiflow
az0re has joined #symbiflow
epony has quit [Quit: reconfiguration]
epony has joined #symbiflow
epony has quit [Max SendQ exceeded]
epony has joined #symbiflow
lkcl has quit [Ping timeout: 260 seconds]
citypw has quit [Ping timeout: 240 seconds]
citypw has joined #symbiflow
lkcl has joined #symbiflow
craigo_ has quit [Ping timeout: 258 seconds]
Bertl_zZ is now known as Bertl
<mithro>
timo - Vivado can't just import VPR output, we have a fasm2bels script which does the conversion into something vivado can read
robert2 has joined #symbiflow
robert2 is now known as rw1nkler
adjtm_ has quit [Remote host closed the connection]
adjtm_ has joined #symbiflow
Bertl is now known as Bertl_oO
citypw has quit [Ping timeout: 240 seconds]
wavedrom has joined #symbiflow
OmniMancer1 has quit [Quit: Leaving.]
rvalles has quit [Ping timeout: 256 seconds]
zzb has joined #symbiflow
rvalles has joined #symbiflow
<_whitenotifier-9>
[sphinx_materialdesign_theme] waywardgeek opened issue #7: Nit: Use higher contrast - https://git.io/Jf3UQ
<sf-slack>
<timo.callahan> anybody: is there any documentation for how to set up your environment to use "fasm2bels.py" ? I have found symbiflow-arch-defs/xc/xc7/fasm2bels/, but I'm not sure what to do with it so that I can do "python3 -mfasm2bels ....".
<litghost>
It's integrated into the build system, as <target>_bitv
<litghost>
It's integrated into the build system, as <target>_bit_v
<sf-slack>
<timo.callahan> Well, the bitstream was generated by Symbiflow, but not under the build/xc/xc7/tests framework, so it looks like there will be some work involved...
craigo_ has joined #symbiflow
rw1nkler has quit [Quit: WeeChat 1.9.1]
<sf-slack>
<timo.callahan> I do have the .fasm and .frames files.
<litghost>
Are you using the install tarball?
<litghost>
If so, then you won't have the needed files
<mithro>
timo: This probably should be written down somewhere! :-P
<sf-slack>
<timo.callahan> litghost: I'm manually running the examples in https://github.com/antmicro/symbiflow-examples. These are originally targetted for testing in CI I think. They are kind of nice since they have a straight-forward Makefile showing each step. But the LiteX test is acting funny, failing memtest, so at Tim's suggestion I was going to read it into Vivado to look at timing (vtr did in fact report negative slack so
<sf-slack>
it looks like it failed timing).
<sf-slack>
<timo.callahan> I think I'll make a new test under xc/xc7/tests, copying the sources from that directory, and compare the output, and also do the bit_v conversion to look at it in Vivado (if it looks like it failed timing the same way).