Thursday, 2020-07-02

*** tpb has joined #symbiflow00:00
*** andrewb1999 has joined #symbiflow01:00
*** kraiskil has quit IRC01:06
*** kgugala has joined #symbiflow01:10
*** andrewb1999 has quit IRC01:13
*** kgugala_ has joined #symbiflow01:47
*** Degi has quit IRC01:48
*** kgugala has quit IRC01:50
*** Degi has joined #symbiflow01:50
*** citypw has joined #symbiflow02:43
*** craigo has quit IRC03:07
*** tcal has quit IRC03:17
*** tcal has joined #symbiflow03:30
*** kgugala has joined #symbiflow05:10
*** kgugala_ has quit IRC05:12
*** mkru has joined #symbiflow05:55
*** kgugala has quit IRC06:42
*** kgugala has joined #symbiflow06:42
*** enriq has joined #symbiflow06:46
*** kgugala_ has joined #symbiflow07:13
*** kgugala has quit IRC07:15
*** enriq has quit IRC07:16
*** OmniMancer has joined #symbiflow07:32
*** epony has quit IRC08:03
*** enriq has joined #symbiflow08:03
*** enriq has quit IRC08:53
*** epony has joined #symbiflow09:02
sf-slack3<dnhkng> Hi, im new here. I have a bit of Vivado experience for a year-long work project (all VHDL/Pynq), and was thinking about using Sybiflow for personal projects09:03
sf-slack3<dnhkng> I was wondering if there are any examples of SERDES code for Series 7 or ECP5?09:05
sf-slack3<dnhkng> I'm used to drag-drop IP blocks in Vivado, so I'm finding this a bit complex09:06
*** enriq has joined #symbiflow09:11
sf-slack3<acomodi> Hi @dnhkng, in symbiflow-arch-defs there are some basic tests for SERDES you can look at and might be helpful. https://github.com/SymbiFlow/symbiflow-arch-defs/tree/master/xc/xc7/tests/serdes09:24
tpbTitle: symbiflow-arch-defs/xc/xc7/tests/serdes at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)09:24
sf-slack3<acomodi> Or, if you want to take a look at a more complex design that uses SERDES you can take a look to litex with DDR. https://github.com/SymbiFlow/symbiflow-arch-defs/tree/master/xc/xc7/tests/soc/litex/mini_ddr09:26
tpbTitle: symbiflow-arch-defs/xc/xc7/tests/soc/litex/mini_ddr at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)09:26
sf-slack3<acomodi> This last design was generated using Litex and the litedram module: https://github.com/enjoy-digital/litedram, https://github.com/enjoy-digital/litex09:27
tpbTitle: GitHub - enjoy-digital/litex: Build your hardware, easily! (at github.com)09:27
sf-slack3<dnhkng> Thanks! I'll go and explore those!09:27
sf-slack3<acomodi> Forgot to mention that these are for Series 7 devices09:30
-_whitenotifier-f- [prjxray] acomodi opened issue #1384: Export fasm2frames and bitstream generation in a separate package - https://git.io/JJU6U10:01
*** epony has quit IRC10:18
*** OmniMancer has quit IRC10:19
*** craigo has joined #symbiflow10:30
*** OmniMancer has joined #symbiflow10:37
*** kraiskil has joined #symbiflow11:55
*** enriq has quit IRC12:53
sf-slack3<mholenko> @timo.callahan the magic wand TFLite demo uses an older version of litex-buildenv that doesn't come with the LiteX timer improvements out-of-the-box; In order to enable those you have to: • backport changes from https://github.com/enjoy-digital/litex/commit/be25500e9173b0e7c0ec6e8d5f626cc7f52a9484#diff-b5263d4f4c7505bfcc3542a76433f256 in LiteX • update the TFLite configuration13:02
sf-slack3(https://github.com/tensorflow/tensorflow/blob/626bb2c4d0bdb626b406c202c2dfd167da586bc6/tensorflow/lite/micro/tools/make/third_party_downloads.inc#L80) to use the Zephyr version with a matching driver (at least https://github.com/zephyrproject-rtos/zephyr/commit/265d2cfa690d93deb7f57d871518b5e31f8f4a8e)13:02
tpbTitle: uptime: rework and integrate it in Timer to ease software support. · enjoy-digital/litex@be25500 · GitHub (at github.com)13:02
tpbTitle: drivers: litex_timer: Fix IRQ lock intolerance · zephyrproject-rtos/zephyr@265d2cf · GitHub (at github.com)13:02
*** kgugala has joined #symbiflow13:10
*** kgugala has quit IRC13:11
*** kgugala has joined #symbiflow13:12
*** kgugala_ has quit IRC13:13
*** kgugala has quit IRC13:20
*** kgugala has joined #symbiflow13:20
*** enriq has joined #symbiflow13:34
*** enriq has quit IRC14:42
*** enriq has joined #symbiflow14:43
*** az0re has quit IRC15:00
*** andrewb1999 has joined #symbiflow15:03
*** _whitenotifier-f has quit IRC15:04
*** proteus-guy has quit IRC15:04
*** sf-slack3 has quit IRC15:07
*** sf-slack has joined #symbiflow15:07
*** tcal has quit IRC15:08
*** tcal_ has joined #symbiflow15:08
*** proteus-guy has joined #symbiflow15:11
*** tcal_ has quit IRC15:12
*** y2kbugger_ has joined #symbiflow15:14
*** Degi has quit IRC15:14
*** andrewb1999 has quit IRC15:14
*** y2kbugger has quit IRC15:14
*** y2kbugger_ is now known as y2kbugger15:14
*** rvalles has quit IRC15:14
*** Degi has joined #symbiflow15:15
*** rvalles has joined #symbiflow15:18
*** az0re has joined #symbiflow15:22
*** _whitelogger has quit IRC15:29
*** _whitelogger has joined #symbiflow15:33
*** citypw has quit IRC15:35
*** andrewb1999 has joined #symbiflow15:45
*** OmniMancer has quit IRC16:26
*** andrewb1999 has quit IRC17:01
*** andrewb1999 has joined #symbiflow17:33
*** epony has joined #symbiflow18:47
*** mkru has quit IRC18:49
*** kraiskil has quit IRC20:08
*** kraiskil has joined #symbiflow20:10
*** kraiskil has quit IRC20:15
*** josi has quit IRC20:43
*** josi has joined #symbiflow20:44
*** lopsided98 has quit IRC20:56
*** lopsided98 has joined #symbiflow20:57
mithroandrewb1999: Can you confirm the db push for https://github.com/SymbiFlow/prjxray-db/compare/master...mithro:master looks right?21:42
tpbTitle: Comparing SymbiFlow:master...mithro:master · SymbiFlow/prjxray-db · GitHub (at github.com)21:42
mithroThe design.json seem to have a new "type": "XXXX" values21:42
mithroandrewb1999: There seems to continue to be instability in the SDF generation21:43
andrewb1999mithro: Yes, the new explicit typing was added to design.json to be able to make my work a pure superset of the roi21:44
mithroandrewb1999: Shall I push it to master then?21:45
andrewb1999mithro: Yes, as long as you're okay with the stuff outside of design.json that has changed21:46
andrewb1999mithro/litghost: I've created a python object to represent an overlay that's essentially the inverse of the roi.py in prjxray and supports cutting out multiple regions.  Should I follow the current roi pattern and add this to prjxray, or should I put it in symbiflow-arch-defs?22:03
*** lopsided98 has quit IRC22:17
mithroandrewb1999: prjxray-db updated22:19
*** lopsided98 has joined #symbiflow22:19
andrewb1999mithro: Thanks!22:34
*** kraiskil has joined #symbiflow23:12
*** enriq has quit IRC23:18
*** kgugala has quit IRC23:28
*** maartenBE has quit IRC23:30
*** maartenBE has joined #symbiflow23:32
*** kgugala has joined #symbiflow23:39
mithroPeople might find the following IEEE issue interesting -- https://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?punumber=4023:52
*** andrewb1999 has quit IRC23:57
*** kgugala has quit IRC23:58

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!