03:12 <digshadow> tmichalak: https://github.com/SymbiFlow/prjxray/issues/11

03:12 <tpb> Title: Document the bitstream for the IOBs in the Artix-7 · Issue #11 · SymbiFlow/prjxray · GitHub (at github.com)

03:12 <digshadow> just updated comment I added

03:19 <OmniMancer> Is there any guidance available for the BRAM patching tool requirements/direction?

03:21 <OmniMancer> This issue https://github.com/SymbiFlow/prjxray/issues/181

03:21 <tpb> Title: Create tool to patch blockram (BRAM) contents in bitstream · Issue #181 · SymbiFlow/prjxray · GitHub (at github.com)

03:31 <litghost> The BRAM contents live in the BLOCK_RAM segments of the bitstream (see https://raw.githubusercontent.com/SymbiFlow/prjxray-db/master/artix7/tilegrid.json). So a tool could use xc7patch to replace frames in those segments with new contents, and a tool could extract that data too.

03:32 <litghost> With tilegrid.json and the block ram segbits (https://github.com/SymbiFlow/prjxray-db/blob/master/artix7/segbits_bram_l.block_ram.db) we do have the mapping of bits in the BLOCK_RAM sections, and their relationship to the BRAM

03:32 <tpb> Title: prjxray-db/segbits_bram_l.block_ram.db at master · SymbiFlow/prjxray-db · GitHub (at github.com)

03:33 <litghost> Some work is required to handle things like parity bits if enabled, and the bits in the segbits do not match the exact bits used in the vivado techmap

03:33 <litghost> The vivado techmap defines 256 bit segments, where as the segbits are a flat linear array

03:36 <OmniMancer> Ah, thanks for the links, I will look at them after LCA and see what I can make of it and ask further questions if I have them

09:04 <nats`> https://github.com/SymbiFlow/prjxray/issues/528 <= I'll take care of that this evening, I'll store it in the run.ok (it'll be moved later when we will move fuzzer results in xml files)

09:04 <tpb> Title: Fuzzer storing last target · Issue #528 · SymbiFlow/prjxray · GitHub (at github.com)

20:58 <litghost> nats: Maybe conside making the build directories and run.ok files suffix with .${XRAY_PART}? Then we could build databases in the same directory structure?

20:58 <litghost> I haven't thought about it too hard, but there is nothing preventing it, and then Make would track the dependencies correctly