| *** tpb has joined #symbiflow | 00:00 | |
| *** OmniMancer has quit IRC | 00:04 | |
| *** _whitelogger has quit IRC | 00:10 | |
| *** _whitelogger has joined #symbiflow | 00:12 | |
| *** OmniMancer has joined #symbiflow | 00:34 | |
| *** OmniMancer has quit IRC | 01:26 | |
| *** whatnick has joined #symbiflow | 01:28 | |
| *** OmniMancer has joined #symbiflow | 01:31 | |
| *** matthusz` has joined #symbiflow | 02:02 | |
| *** matthusz` has quit IRC | 02:11 | |
| *** whatnick has quit IRC | 02:32 | |
| digshadow | tmichalak: https://github.com/SymbiFlow/prjxray/issues/11 | 03:19 |
|---|---|---|
| tpb | Title: Document the bitstream for the IOBs in the Artix-7 · Issue #11 · SymbiFlow/prjxray · GitHub (at github.com) | 03:19 |
| digshadow | just updated comment I added | 03:19 |
| OmniMancer | Is there any guidance available for the BRAM patching tool requirements/direction? | 03:26 |
| OmniMancer | This issue https://github.com/SymbiFlow/prjxray/issues/181 | 03:28 |
| tpb | Title: Create tool to patch blockram (BRAM) contents in bitstream · Issue #181 · SymbiFlow/prjxray · GitHub (at github.com) | 03:28 |
| 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:38 |
| 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:39 |
| tpb | Title: prjxray-db/segbits_bram_l.block_ram.db at master · SymbiFlow/prjxray-db · GitHub (at github.com) | 03:39 |
| 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:40 |
| litghost | The vivado techmap defines 256 bit segments, where as the segbits are a flat linear array | 03:40 |
| 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 | 03:43 |
| *** citypw has joined #symbiflow | 03:52 | |
| *** whatnick has joined #symbiflow | 04:31 | |
| *** OmniMancer has quit IRC | 05:08 | |
| *** OmniMancer has joined #symbiflow | 05:22 | |
| *** OmniMancer has quit IRC | 05:41 | |
| *** OmniMancer has joined #symbiflow | 05:45 | |
| *** OmniMancer has quit IRC | 06:08 | |
| 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:11 |
| tpb | Title: Fuzzer storing last target · Issue #528 · SymbiFlow/prjxray · GitHub (at github.com) | 09:11 |
| *** OmniMancer has joined #symbiflow | 10:59 | |
| *** DontShoot has joined #symbiflow | 12:39 | |
| *** DontShoot has left #symbiflow | 12:41 | |
| *** OmniMancer has quit IRC | 13:39 | |
| *** citypw has quit IRC | 14:26 | |
| *** _whitelogger has quit IRC | 20:52 | |
| *** _whitelogger has joined #symbiflow | 20:54 | |
| 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? | 21:05 |
| litghost | I haven't thought about it too hard, but there is nothing preventing it, and then Make would track the dependencies correctly | 21:05 |
| *** Rahix has joined #symbiflow | 22:14 | |
Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!