Tuesday, 2023-01-03

*** tpb <[email protected]> has joined #litex00:00
*** Degi <[email protected]> has quit IRC (Ping timeout: 272 seconds)02:08
*** Degi <[email protected]> has joined #litex02:09
*** bl0x_ <[email protected]> has joined #litex02:55
*** bl0x <[email protected]> has quit IRC (Ping timeout: 264 seconds)02:57
*** FabM <FabM!~FabM@2a03:d604:103:600:2e60:8c7c:e8fb:7990> has joined #litex06:25
DerekKozel[m]Hey _florent_, Back in 2020 you ordered a Pluto SDR. Did you ever turn it on?13:21
gurkiDerekKozel[m]: if you ask a specific question ppl might be able to help ;)13:33
DerekKozel[m]Hi Gurki. I have some Plutos and was curious if anyone had setup LiteX with it.13:36
DerekKozel[m]Answering some of my own question Florent made a very basic platform file in April last year, Just with a few GPIO defined.13:37
DerekKozel[m]https://github.com/litex-hub/litex-boards/commits/master/litex_boards/targets/adi_plutosdr.py13:37
DerekKozel[m]Actually bringing up the AD9364 RF frontend would be a bunch of work (I assume), though nothing new for LiteX as there are already designs using the same RFIC13:38
gurkiah. i cant help with litex stuff, i just happen to own and use a pluto13:45
gurkii assume youre aware of https://github.com/analogdevicesinc/plutosdr-fw13:45
*** knicklicht <knicklicht!~knicklich@2a02:908:1995:4220:70f3:c252:5da2:5b80> has joined #litex14:16
knicklichtHey, can someone tell me why I get timing issues when I try to build ./litex_boards/targets/colorlight_5a_75x.py --cpu-type vexriscv --with-ethernet --csr-json csr.json --build. I get the following warnings:14:18
knicklichtWarning: Max frequency for clock                  '$glbnet$crg_clkout0': 59.92 MHz (FAIL at 60.00 MHz)14:18
knicklichtWarning: Max frequency for clock '$glbnet$eth_clocks0_rx$TRELLIS_IO_IN': 112.76 MHz (FAIL at 125.00 MHz)14:18
knicklichtThe closed github issues seem to indicate, that liteeth should work on ECP5 FPGAs.14:18
sensilleknicklicht: i had better success with yosys from oss-cad-suite-2022040714:20
sensillebut you have to experiment with some tuning. timing closure is possible, but it also failed for me out of the box14:20
knicklichtThanks, I will try the alternative version of yosys. How do I go about tuning the core?14:21
sensillei just tried some recommended yosys setting. not sure if i can still find them14:22
sensilleone thing to try is "scratchpad -copy abc9.script.flow3 abc9.script; synth_ecp5 -abc9"14:24
sensilleor just "synth_ecp5 -abc"14:25
sensille*abc914:25
knicklichtOkay, I will have to get familiar with yosys first. I wouldn't know where to set this14:25
knicklichtis it correct that I use --with-ethernet and not --with-etherbone?14:29
sensilledepends on what you want to achieve. shouldn't have an impact on the 120mhz timing14:30
sensilleregarding the 60mhz you might also just reduce the target to 50mhz14:31
knicklichtI want to run zephyr on the vexriscv14:32
sensille--with-ethernet means you do ip in software, to whatever extent14:33
sensille--with-etherbone means ethernet is handled autonomously by gateware and you only map memory regions which you can access over network14:34
knicklichtOkay, so for my use case --with-ethernet makes sense14:34
sensillei guess you can run zephyr in both variants, but i have no experience with zephyr14:34
knicklichtOkay, thanks that helped anyways. The oss-cad-suite build got 60.47 MHz out of the box. I now only need to figure out how to get from 97.26 Mhz to 125MHz14:36
sensillethat's the more important part14:36
knicklichtWhere do I set the "scratchpad synth_ecp5 -abc"?14:37
sensillefor a test you can manually edit colorlite.ys14:39
knicklichtWhich I can find where? Sorry, I am absolutely new to Lattice FPGAs14:43
sensillebuild/gateware/14:43
sensilleit is automatically generated14:43
knicklichtSo I need to interrupt the build process right after the file is generated? If I just rebuild with the "-abc9" added, the file is just overwritten14:50
sensillei think after the build is done, you can go to build/gateware, change colorlite.ys and call build_colorlite.sh14:51
sensilleknicklicht: 123.46 MHz (FAIL at 125.00 MHz). close ...15:04
knicklichtYou are my personal hero:-)  .That worked. I now have 126Mhz. The clock is at 55.96Mhz, I'll just set the clock to 50MHz15:04
sensille\o/15:04
sensilleremember that yosys uses a random seed, so results may vary from run to run15:05
knicklichtI saw that. Maybe I'll rerun a few times until I get 60MHz15:05
sensilleyou can pass in a seed15:06
knicklichtdo I pass it to synth_ecp5 as well?15:07
sensillenot sure15:08
*** knicklicht <knicklicht!~knicklich@2a02:908:1995:4220:70f3:c252:5da2:5b80> has quit IRC (Ping timeout: 260 seconds)16:43
*** TMM_ <[email protected]> has quit IRC (Quit: https://quassel-irc.org - Chat comfortably. Anywhere.)20:13
*** TMM_ <[email protected]> has joined #litex20:13
*** FabM <FabM!~FabM@armadeus/team/FabM> has quit IRC (Ping timeout: 255 seconds)20:58
*** zjason`` <zjason``[email protected]> has joined #litex21:23
*** zjason` <zjason`[email protected]> has quit IRC (Ping timeout: 264 seconds)21:25
*** mlaga97 <mlaga97!~quassel@user/mlaga97> has joined #litex21:30
*** feldim2425_ <feldim2425_!~feldim242@2001:871:25a:803d:e6d8:4e00:bb6a:7c4> has joined #litex23:34
*** feldim2425 <[email protected]> has quit IRC (Ping timeout: 272 seconds)23:34

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