<litghost>
daveshah: No, mithro made that push, I'm not sure where it came from exactly
<litghost>
daveshah: I believe we switched from the z7010 to z7020 as the base part, but that shouldn't have changed the IOB output
<litghost>
daveshah: Looks like something affected the solution for the LIOB33.IOB_Y0, which is likely the presence of "weird" IOB's that don't behavior like other IOB's
<daveshah>
That makes sense, as Y1 is fine
OmniMancer has joined #symbiflow
<litghost>
daveshah: If you need a short term workaround, the a7 and z7 bits looks to be compatible
<daveshah>
No worries, I have just reverted that file to older z7 db for now, but I'll bear that in mind
<sf-slack>
<acomodi> litghost, daveshah: could be possible. In z7020 there is only one column of LIOB33s, which are not as many as the one in artix7. Maybe the fuzzer is intended to have more of LIOBs to correctly get all the bits
<sf-slack>
<acomodi> By column I mean clock region, the other two clock regions above do not have LIOB33, because of the PSS
Bertl_zZ is now known as Bertl
freemint has joined #symbiflow
kraiskil has quit [Ping timeout: 265 seconds]
<mithro>
morning daveshah
<mithro>
Can someone log a github issue about the IO bits for zynq7
<sf-slack>
<acomodi> I'm on it
space_zealot has quit [Ping timeout: 260 seconds]
<_whitenotifier-3>
[prjxray] acomodi opened issue #1234: IOB bits removed from recent DB update - https://git.io/JvWHI
freemint has quit [Ping timeout: 240 seconds]
freemint has joined #symbiflow
space_zealot has joined #symbiflow
space_zealot has quit [Remote host closed the connection]
space_zealot has joined #symbiflow
freemint has quit [Ping timeout: 265 seconds]
freemint has joined #symbiflow
freemint has quit [Remote host closed the connection]
OmniMancer has quit [Quit: Leaving.]
kraiskil has joined #symbiflow
kraiskil has quit [Read error: Connection reset by peer]