09:03 <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 projects

09:05 <sf-slack3> <dnhkng> I was wondering if there are any examples of SERDES code for Series 7 or ECP5?

09:06 <sf-slack3> <dnhkng> I'm used to drag-drop IP blocks in Vivado, so I'm finding this a bit complex

09:24 <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/serdes

09:24 <tpb> Title: symbiflow-arch-defs/xc/xc7/tests/serdes at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)

09:26 <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_ddr

09:26 <tpb> Title: symbiflow-arch-defs/xc/xc7/tests/soc/litex/mini_ddr at master · SymbiFlow/symbiflow-arch-defs · GitHub (at github.com)

09:27 <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/litex

09:27 <tpb> Title: GitHub - enjoy-digital/litex: Build your hardware, easily! (at github.com)

09:27 <sf-slack3> <dnhkng> Thanks! I'll go and explore those!

09:30 <sf-slack3> <acomodi> Forgot to mention that these are for Series 7 devices

10:01 <_whitenotifier-f> [prjxray] acomodi opened issue #1384: Export fasm2frames and bitstream generation in a separate package - https://git.io/JJU6U

13:02 <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 configuration

13: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 <tpb> Title: uptime: rework and integrate it in Timer to ease software support. · enjoy-digital/litex@be25500 · GitHub (at github.com)

13:02 <tpb> Title: drivers: litex_timer: Fix IRQ lock intolerance · zephyrproject-rtos/zephyr@265d2cf · GitHub (at github.com)

21:42 <mithro> andrewb1999: Can you confirm the db push for https://github.com/SymbiFlow/prjxray-db/compare/master...mithro:master looks right?

21:42 <tpb> Title: Comparing SymbiFlow:master...mithro:master · SymbiFlow/prjxray-db · GitHub (at github.com)

21:42 <mithro> The design.json seem to have a new "type": "XXXX" values

21:43 <mithro> andrewb1999: There seems to continue to be instability in the SDF generation

21:44 <andrewb1999> mithro: Yes, the new explicit typing was added to design.json to be able to make my work a pure superset of the roi

21:45 <mithro> andrewb1999: Shall I push it to master then?

21:46 <andrewb1999> mithro: Yes, as long as you're okay with the stuff outside of design.json that has changed

22:03 <andrewb1999> mithro/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:19 <mithro> andrewb1999: prjxray-db updated

22:34 <andrewb1999> mithro: Thanks!

23:52 <mithro> People might find the following IEEE issue interesting -- https://ieeexplore.ieee.org/xpl/mostRecentIssue.jsp?punumber=40