<FFY00>
if we choose to use this it might be worth to hosting a self-runner
<FFY00>
*to host
futarisIRCcloud has quit [Quit: Connection closed for inactivity]
<FFY00>
well, it's failing, I think because of missing disk space :/
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #symbiflow
FFY00 has quit [Max SendQ exceeded]
FFY00 has joined #symbiflow
Ultrasauce has quit [Ping timeout: 240 seconds]
Ultrasauce has joined #symbiflow
<_whitenotifier-3>
[symbiflow-arch-defs] rakeshm75 opened issue #1431: Branch : Quicklogic : Different ports and port names in top_bit.v file compared to the design file - https://git.io/JfTvX
proteus-guy has quit [Ping timeout: 256 seconds]
FFY00 has quit [Remote host closed the connection]
FFY00 has joined #symbiflow
proteus-guy has joined #symbiflow
kraiskil has quit [Ping timeout: 260 seconds]
<_whitenotifier-3>
[symbiflow-arch-defs] mkurc-ant opened issue #1432: Add support for IDDR primitives - https://git.io/JfTTn
<mithro>
By "VTR's github address" what you mean for that?
<mithro>
litghost: Ahh, it should be automatically redirected at the moment
<litghost>
Oh, ok
_whitenotifier-3 has quit [Ping timeout: 260 seconds]
QDX45 has joined #symbiflow
FFY00 has quit [Read error: Connection reset by peer]
FFY00 has joined #symbiflow
OmniMancer has joined #symbiflow
<sf-slack>
<haskal> prjxray question: how do the bram segbits work, particularly how do the init strings for a ramb36 correspond to init strings for the 2 component ramb18 elements?
<sf-slack>
<haskal> i have a test bitstream for zynq7 that divides a 32 bit block memory space into 1 ramb36 element per bitlane, that i populated with a basic bram mem file that has 512 words of 00000001, so all the set bits go into a single one of the bram elements
<sf-slack>
<haskal> i can see in the debug output of updatemem that there is a INIT_00 and INIT_01 for one of the bram elements with all bits set, as expected, however the resulting bitstream appears to have the bits set across only 2 of the frames
<sf-slack>
<haskal> i had assumed the ramb18s get concatenated into the ramb36, and if this were the case it should take 4 frames for this data
<mithro>
haskal: Did you see the ram patching tool?