<duck2> latest symbiflow-arch-defs and conda vpr prints ~140K warnings to the output while building buttons_basys3_bin. am i doing something wrong?
space_zealot has joined #symbiflow
space_zealot has quit [Read error: Connection reset by peer]
proteusguy has quit [Remote host closed the connection]
Bertl is now known as Bertl_zZ
citypw has joined #symbiflow
citypw has quit [Ping timeout: 258 seconds]
<mithro> duck2: You are right about the output be hilarious! http://dpaste.com/2AF5DWF.txt
<mithro> duck2: No, you should log a bug about that
<mithro> duck2: (Regarding the vtr errors)
proteusguy has joined #symbiflow
proteusguy has quit [Remote host closed the connection]
OmniMancer has joined #symbiflow
futarisIRCcloud has joined #symbiflow
<sf-slack2> <acomodi> duck2, mithro: There is an open PR I am dealing with to make the error/warnings optional: https://github.com/SymbiFlow/vtr-verilog-to-routing/pull/66
<tpb> Title: [WIP] vpr: added optional vpr_throw to demote errors to warnings by acomodi · Pull Request #66 · SymbiFlow/vtr-verilog-to-routing · GitHub (at github.com)
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
citypw has joined #symbiflow
citypw has quit [Client Quit]
proteusguy has joined #symbiflow
proteusguy has quit [Remote host closed the connection]
futarisIRCcloud has joined #symbiflow
Bertl_zZ is now known as Bertl
Miyu has joined #symbiflow
hackkitten has quit [Ping timeout: 252 seconds]
Miyu is now known as hackkitten
proteusguy has joined #symbiflow
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<sf-slack2> <mkurc> @mithro I checked Verilator for attribute support and it seems that all cases relevant to us (parameters and port connections) are supported.
<sf-slack2> <mkurc> @mithro There is still no feedback on my PR to the Icarus Verilog.
<sf-slack2> <mkurc> @mithro Have you consulted with Yosys devs the idea of having wires that mock parameters? (for having attributes on them and preserving default assigned value) Are they willing to accept such a solution?
OmniMancer has quit [Quit: Leaving.]
<mithro> mkurc: Do you want to chat with Eddie directly?
<sf-slack2> <mkurc> @mithro It makes sense. But unfortunately I don't have time for it today.
<mithro> mkruc: I sent an introduction
<sf-slack2> <mkurc> @mitho: Saw it. Thanks.
<hackerfoo> It looks like no IOI bits need to set to pass the signal through. I built "buttons" with Vivado, then converted to FASM, and then back to bitstream without the ROI bitstream, and it works. There are no IOI features in the FASM, just IOB. So I can ignore the IO logic for now.
<litghost> hackerfoo: Yes
<litghost> hackerfoo: Make sure when you do those kind of experiments you run bit2fasm with "--verbose" to ensure unknown bits are reported
<litghost> hackerfoo: There should be 0 of them, but best to check
<hackerfoo> litghost: I did, and there were no unknown bits.
<tpb> Title: prjxray-db/design.json at master · SymbiFlow/prjxray-db · GitHub (at github.com)
<litghost> ZINV_D
<litghost> hackerfoo: Otherwise ILOGIC will invert the signal
<litghost> hackerfoo: It is worth noting that there is no way to actually invert IBUF signals without the use of an IDDR, which is not going to be the baseline ROI breakout
<hackerfoo> Why is it IOB_* instead of IOI_*?
<litghost> hackerfoo: Frankly there is not a strong way to seperate the too from a bitstream perspective, so the initial IOB/IOI fuzzers emit a mix of both
<litghost> hackerfoo: I don't know if tilegrid even has an entry for IOI tiles yet, as they overlap strongly with the IOB bits
<litghost> Example:
<litghost> IOB -> RIOB33.IOB_Y0.INOUT 30_67
<litghost> IOI -> RIOB33.IOB_Y0.OSERDESE.DATA_WIDTH.2 30_127
<litghost> hackerfoo: So we can restructure the fuzzers and tilegrid, but the bits are strongly interwoven
tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow