<digshadow> FWIW I almost exclusively dealt with bit definitions. If you have a routing question, I'm probably not the person to ask
<digshadow> Also timing
<digshadow> Ex: if you have questions about RAM32X1S bitstream encoding I can provide insight there
<hackerfoo> Well, is this what you expect? The data input line goes to DI2, and the data output to O6.
<digshadow> hackerfoo: looking at the user guide, two observations. First, the DI naming is very confusing with net DID[0] => pin DID2, net DID[1] => pint DID1. That aside, it notes in a few things (ex: "Figure 2-11: 64 X 3 Simple Dual Port Distributed RAM (RAM64M)") that they go to pin DI1 when only one is used
<digshadow> If its unclear though, I'd probably make a minitest with a number of configurations (or using existing minitests) and take a look at the routing in the various configurations
<digshadow> Let me see whats in the minitests dir...
<digshadow> Yeah if you synthesize prjxray/fuzzers/018-clb-ram/minitest, maybe modifying it to use the commented out top module
<digshadow> you should get a bunch of different examples
<digshadow> nvm no modification needed, just synthesize it
_whitelogger has joined #symbiflow
<hackerfoo> digshadow: Thanks. I'll look at it a little later if I can.
futarisIRCcloud has joined #symbiflow
Bertl_oO is now known as Bertl_zZ
citypw has joined #symbiflow
tmichalak1 has quit [Read error: Connection reset by peer]
kraiskil has joined #symbiflow
proteusguy has quit [Remote host closed the connection]
proteusguy has joined #symbiflow
jevinskie has joined #symbiflow
proteusguy has quit [Ping timeout: 258 seconds]
kraiskil has quit [Read error: No route to host]
kraiskil has joined #symbiflow
proteusguy has joined #symbiflow
Vonter has quit [Ping timeout: 255 seconds]
<tpb> Title: WIP - utils/vlog: More tests from timing tutorial. by mithro · Pull Request #645 · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<sf-slack2> <kgugala> sure
<sf-slack2> <kgugala> what is left there?
<sf-slack2> <kgugala> Is it only making the CI green, or some features are missing?
<mithro> kgugala: It's a bit unclear, I think most of the work is figuring out what they are *suppose* to be doing :-P
<sf-slack2> <kgugala> ah, OK
<tpb> Title: v2x solve issues to have working tests · Issue #599 · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<mithro> kgugala: I don't understand why the $dff cells which are generated by the 'proc' pass are getting ignored?
<tpb> Title: symbiflow-arch-defs/json.py at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<mithro> tmichalak : I merged https://github.com/SymbiFlow/prjxray/pull/788 as the CI was green
<tpb> Title: Disable currently flaky fuzzers to make CI go green again by tmichalak · Pull Request #788 · SymbiFlow/prjxray · GitHub (at github.com)
<sf-slack2> <tmichalak> @mithro: great, I also solved the problem with 052-pip-clkin ( https://github.com/SymbiFlow/prjxray/pull/799). At least I think so.
<tpb> Title: 052-pip-clkin: stabilize and re-enable the fuzzer by tmichalak · Pull Request #799 · SymbiFlow/prjxray · GitHub (at github.com)
<sf-slack2> <kgugala> @mithro yes, this may be problem
<sf-slack2> <kgugala> I'll play around and see what is happening there
<mithro> kgugala: Did you see my comments on https://github.com/SymbiFlow/symbiflow-arch-defs/issues/642 ?
<tpb> Title: Make v2x produce the new composable interconnect specification again (IE Revert #637). · Issue #642 · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<sf-slack2> <tmichalak> @mithro: currently I am running my tests for 054-pip-fan-alt (https://github.com/SymbiFlow/prjxray/pull/789) and started looking into reenabling 045-hclk-cmt-pips (https://github.com/SymbiFlow/prjxray/issues/790)
<tpb> Title: [WIP] 054-pip-fan-alt: stabilize the fuzzer by tmichalak · Pull Request #789 · SymbiFlow/prjxray · GitHub (at github.com)
Vonter has joined #symbiflow
<sf-slack2> <kgugala> @mithro yes, I've seen them
<mithro> kgugala: Did they make sense?
<sf-slack2> <kgugala> this makes sense
<sf-slack2> <kgugala> the question is if that won't break the current flow?
<sf-slack2> <kgugala> I'm using v2x to generate all the xmls and uipdate them with timings
<sf-slack2> <kgugala> so introducing this change now may break arch-defs
<mithro> kgugala: What do you mean?
<tpb> Title: ice40: Adding real world timing values. · mithro/symbiflow-arch-defs@4c996d5 · GitHub (at github.com)
<sf-slack2> <acomodi> mithro: regarding https://github.com/SymbiFlow/symbiflow-arch-defs/issues/642, all the golden pb_types/model should be in the `new` format, am I correct? Than the `xmlsort.xsl` handles the translation to the `old` format to have the interconnects compatible with current VPR
<tpb> Title: Issues · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)
<mithro> acomodi: Yes
<sf-slack2> <acomodi> mithro: ok, got it, I'll revert the PR then
<sf-slack2> <kgugala> @mithro In parallel I'm working on bel timings import into arch.xml. There I switched from handwritten xmls to the ones generated from verilog (I discussed that with @elms and @litghost). Now, with v2x handling multiple instances I should be able to finish this
<sf-slack2> <kgugala> @mithro but if we switch to a new interconnect generation, wouldn't it break the flow?
<sf-slack2> <kgugala> can vpr handle the new interconnect format?
<mithro> kgugala: See what acomodi said -- The `xmlsort.xsl` handles the translation to the `old` format to have the interconnects compatible with current VPR
<mithro> kgugala: Which is done as part of the architecture merging step
<sf-slack2> <kgugala> oh
<sf-slack2> <kgugala> OK
<sf-slack2> <kgugala> I must have missed that
<mithro> kgugala: VPR doesn't handle <xi:include> either
<sf-slack2> <acomodi> mithro: here there is the revert PR https://github.com/SymbiFlow/symbiflow-arch-defs/pull/648, it needs some changes though as I have noticed it creates incorrect direct connections
<sf-slack2> <tmichalak> kokoro seems to be stuck, force-run tag doesn't work, anyone else experiences this problem? I wonder if there is anything else I can do except wait...
<sf-slack2> <mkurc> @tmichalak I made a PR to arch-defs an hour ago and the kokoro seems to be still running. I don't know if I can see logs of a pending build.
<sf-slack2> <tmichalak> @mkurc: maybe the problem only applies to new runs only, let me know if your run finishes
<sf-slack2> <acomodi> Could it be due to the fact that there are multiple PRs that are being run on kokoro?
<sf-slack2> <tmichalak> @acomodi: actually I start to think that it is indeed the case
<sf-slack2> <acomodi> for instance I opened a PR as well a half an hour ago
<sf-slack2> <mkurc> Might be so. It would be nice to have a interface to see load of the build server.
<sf-slack2> <tmichalak> @acomodi: I noticed that when running multiple PRs for fuzzers stabilization there were some hickups in kokoro's runs
<sf-slack2> <tmichalak> @mkurc: I agree
kraiskil has quit [Read error: No route to host]
citypw has quit [Ping timeout: 258 seconds]
kraiskil has joined #symbiflow
auscompgeek has joined #symbiflow
<sf-slack2> <mkurc> @tmichalak Kokoro finished checking my PR successfully
<sf-slack2> <tmichalak> @mkurc: okay thanks, so I have 2 PRs running, i.e. one running and the second one about to run with the use of the force-run tag. Unfortunately, nothing changes for 2 hours now.
<sf-slack2> <acomodi> There is no way right now to run only one of the different checks right? (e.g. XC7-presubmit failed and I want to re-run only that one)
<sf-slack2> <kgugala> I don't think so
<sf-slack2> <kgugala> just rerun all of them
proteusguy has quit [Ping timeout: 250 seconds]
Vonter has quit [Ping timeout: 245 seconds]
Vonter has joined #symbiflow
proteusguy has joined #symbiflow
proteusguy has quit [Remote host closed the connection]
kraiskil has quit [Read error: No route to host]
kraiskil has joined #symbiflow
Bertl_zZ is now known as Bertl
<sf-slack2> <acomodi> update on equivalent tiles: I have update the PR https://github.com/SymbiFlow/vtr-verilog-to-routing/pull/36. Now the placer can swap the blocks in equivalent tiles as well. CI still fails as the arch files do not include the tiles tag.
<tpb> Title: Sign in to GitHub · GitHub (at github.com)
<sf-slack2> <acomodi> By running the `ff_ce_sr` tests I got into a fasm2frames issue
<sf-slack2> <acomodi> `prjxray.fasm_assembler.FasmInconsistentBits: FASM line "CLBLM_R_X5Y117.SLICEL_X1.DOUTMUX.O5" wanted to clear bit (131743, 35, 21) but was set by FASM line "CLBLM_R_X5Y117.SLICEL_X1.DOUTMUX.D5Q"`
<sf-slack2> <acomodi> the tests that work right now are: `chain_packing`, `simple_ff` and `buttons`
Bertl is now known as Bertl_oO
<hackerfoo> I was reading through the CLB user guide last night that the software is responsible for setting A6 high in 32 bit RAM modes to keep O5/O6 independent.
<hackerfoo> I also made VPR use O5 and got a different alternating pattern.
kraiskil has quit [Ping timeout: 246 seconds]
kraiskil has joined #symbiflow
<sf-slack2> <acomodi> `counter` also is working
citypw has joined #symbiflow
proteusguy has joined #symbiflow
citypw has quit [Ping timeout: 258 seconds]
jevinskie has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
_whitelogger has joined #symbiflow
<hackerfoo> Does anyone have a partial reconfiguration license for Vivado? Any plans for SymbiFlow to do partial reconfiguration?
<hackerfoo> Nevermind, it's mentioned right here: https://symbiflow.github.io/#xray
<tpb> Title: SymbiFlow - the GCC of FPGAs (at symbiflow.github.io)
kraiskil has quit [Ping timeout: 246 seconds]
tpb has quit [Remote host closed the connection]
tpb has joined #symbiflow