<digshadow>
nats`: have some more time now. Let me know if you still have any qs
<digshadow>
litghost is a better contact for 07x series, but I can try to answer qs
citypw has joined #symbiflow
citypw has quit [Ping timeout: 258 seconds]
<nats`>
I'll write the splitted version this evening to test it I think it could work correctly and I'll also try with 2018 to see if the leak is still here
<digshadow>
nats`: FYI we are locked to 2017.2 unless something really critical comes pu
<digshadow>
up
storm_ has quit [Quit: Page closed]
<nats`>
yep remember that :)
<nats`>
but I wanted to see if I can run it on 2018
<nats`>
just you know to know :D
sxpert has quit [Ping timeout: 250 seconds]
sxpert has joined #symbiflow
igorangst has joined #symbiflow
<digshadow>
litghost: I'm fixing / reviewing IOB_SIGN issue I saw a while back
<digshadow>
tentatively, looks like this will result in a *negative tilegrid offset*
<digshadow>
do you have any fundamental objections to this?
<digshadow>
the issue is that only half of the normal tile is present, both as displayed in the GUi and in the bitstream
<digshadow>
as the normal tile is 4 words high, but we only have the Y1 case
<digshadow>
I fully expect this to at least break some of our tools on prints
igorangst has quit [Ping timeout: 258 seconds]
igorangst has joined #symbiflow
efg has joined #symbiflow
igorangst has quit [Ping timeout: 246 seconds]
<litghost>
> tentatively, looks like this will result in a *negative tilegrid offset* -> Why not base the tile at the lower address, and shift everybody else up?
<litghost>
Ultimately I don't actually care about a negative offset, as long as fasm2frames.py does the right thing, and xc7patch accepts the input
<litghost>
If you can round trip (bit -> fasm -> bit -> fasm) with no errors, than I'm good
<digshadow>
litghost: its the word offset, not the tile address
<digshadow>
we're out of things to go back to
<litghost>
A negative word offset just causes the frame address to drop below the base address, so shifting the base address down would resolve that.
<digshadow>
litghost: hmm not sure I agree with that
<digshadow>
it would at the very least introduce a lot more special cases than it would solve
<digshadow>
in any case, I just tested with segprint and the iob fuzzer
<digshadow>
and both seemed happy with it
<digshadow>
I'll put the details in the PR for you to review
<digshadow>
push back if you think it will be problematic