| *** tpb <[email protected]> has joined #symbiflow | 00:00 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:8599:2585:a3aa:dbc1> has quit IRC (Quit: Disconnected) | 00:51 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:7ad9:d65f:2504:4b3b> has joined #symbiflow | 00:52 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 00:52 | |
| *** TMM_ <[email protected]> has joined #symbiflow | 00:52 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:7ad9:d65f:2504:4b3b> has quit IRC (Ping timeout: 264 seconds) | 01:01 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:7ad9:d65f:2504:4b3b> has joined #symbiflow | 01:08 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:7ad9:d65f:2504:4b3b> has quit IRC (Quit: No Ping reply in 180 seconds.) | 05:28 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:ba27:ebff:fe5e:6b6e> has joined #symbiflow | 05:29 | |
| *** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.) | 13:51 | |
| *** TMM_ <[email protected]> has joined #symbiflow | 13:51 | |
| *** adjtm <[email protected]> has quit IRC (Read error: Connection reset by peer) | 14:26 | |
| *** adjtm <[email protected]> has joined #symbiflow | 14:26 | |
| *** adjtm <[email protected]> has quit IRC (Read error: Connection reset by peer) | 14:30 | |
| *** adjtm <[email protected]> has joined #symbiflow | 14:30 | |
| *** adjtm <[email protected]> has quit IRC (Remote host closed the connection) | 17:48 | |
| *** adjtm <[email protected]> has joined #symbiflow | 17:48 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:ba27:ebff:fe5e:6b6e> has quit IRC (Ping timeout: 245 seconds) | 19:45 | |
| *** lopsided98 <lopsided98!~quassel@2601:18a:0:85e0:ba27:ebff:fe5e:6b6e> has joined #symbiflow | 19:45 | |
| sf-slack1 | <syed.ahmed.emails> @gatecat Have you ever seen an error like this on nextpnr-xilinx: ```prjxray.fasm_assembler.FasmLookupError: Segment DB RIOI3_TBYTESRC, key RIOI3_TBYTESRC.OLOGIC_Y0.OSERDES.DATA_WIDTH.W8 not found from line 'RIOI3_TBYTESRC_X105Y157.OLOGIC_Y0.OSERDES.DATA_WIDTH.W8' Segment DB RIOI3_TBYTESRC, key RIOI3_TBYTESRC.OLOGIC_Y0.OSERDES.DATA_WIDTH.DDR.W6_8 not found from line | 20:28 |
|---|---|---|
| sf-slack1 | 'RIOI3_TBYTESRC_X105Y157.OLOGIC_Y0.OSERDES.DATA_WIDTH.DDR.W6_8' Segment DB RIOI3_TBYTESRC, key RIOI3_TBYTESRC.OLOGIC_Y0.OSERDES.DATA_WIDTH.SDR.W2_4_5_6 not found from line 'RIOI3_TBYTESRC_X105Y157.OLOGIC_Y0.OSERDES.DATA_WIDTH.SDR.W2_4_5_6' ...``` I know nextpnr-xilinx is not stable yet but was just trying to see how much is possible using litex+yosys+vpr vexrisc app. | 20:28 |
| sf-slack1 | <kgugala> @say | 20:41 |
| sf-slack1 | <kgugala> @syed.ahmed.emails do you use nextpnr or VPR ? | 20:42 |
| sf-slack1 | <kgugala> I got a little bit confused | 20:42 |
| sf-slack1 | <syed.ahmed.emails> my current benchmarks use vpr, but I was trying to run them with nextpnr-xilinx | 20:49 |
| sf-slack1 | <syed.ahmed.emails> the benchmark routed but during bitstream generation I get this error | 20:49 |
| sf-slack1 | <syed.ahmed.emails> I did a write_json before VPR techmapping (in the current symbiflow-examples/vpr flow) and then loaded that json in the nextpnr-xilinx to do the place and route for a200t. | 20:51 |
| sf-slack1 | <kgugala> the error looks like nextpnr emits a FASM entry that is not in the prjxray database | 21:10 |
| sf-slack1 | <kgugala> I believe we know all the bits in RIOI3, so I'd assume there is a bug in nextpnr emitting those lines incorrectly | 21:11 |
| sf-slack1 | <syed.ahmed.emails> thanks! that helps. | 21:19 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!