Tuesday, 2019-10-15

*** tpb has joined #litex00:00
*** y2kbugger has quit IRC00:17
*** rohitksingh has quit IRC00:33
*** somlo has quit IRC00:44
*** y2kbugger has joined #litex00:56
*** rohitksingh has joined #litex01:45
*** Dolu has quit IRC02:03
*** freemint has quit IRC02:14
*** rohitksingh has quit IRC02:25
*** y2kbugger has quit IRC02:46
*** rohitksingh has joined #litex03:18
*** somlo has joined #litex03:39
*** rohitksingh has quit IRC03:57
*** rohitksingh has joined #litex04:09
*** shenki has quit IRC04:14
*** rohitksingh has quit IRC05:19
*** shenki has joined #litex05:31
*** rohitksingh has joined #litex06:31
*** RaYmAn_ has joined #litex08:26
kbeckmann_florent_: thanks for the reply! yeah that makes a lot of sense, migrating is probably a pretty high risk in its own. being able to use nMigen modules together with litex sounds like a good start.08:41
*** rohitksingh has quit IRC09:01
*** freemint has joined #litex10:34
*** Dolu has joined #litex11:44
somlodaveshah: this is going to start out as a high level, dumb-user question... Back about a month ago, I used to be able to sometimes reach 60MHz for Litex+Rocket on the versa (with -abc9 -nowidelut and the xc7dsp patch, still a PR at the time). FWIW, commits were yosys #c7f1368, trellis #f692269, nextpnr #927077e.14:40
somloWith recent versions (right now it's yosys #2daa568, trellis #e2e10bf, nextpnr #c365dd1 but I've been about it for the last week or so) I'm only reaching about 10MHz less on average, and couldn't hit 60MHz after running the build in a loop over the last 24+ hours.14:40
somloIs there something else I should try, flag-wise, and/or do you know of a possible explanation as to why the average Fmax would have dropped by 10MHz?14:41
somloSorry, I know it's not a lot to go on :)14:41
daveshahI can only think it's related to the 36-bit BRAM change14:47
daveshahI can't think why that would reduce Fmax though14:47
acathlasomlo, any debug wire left somewhere?15:17
somlodaveshah: maybe I'm just unlucky, 60MHz was never a straightforward, reliable outcome; it's just that I've been looping harder and longer than I remember before without managing to land on one...15:34
somloacathla: same design as before, no additional debug wires added in recent memory :)15:34
somlodaveshah: maybe I should just focus on the trellis board and forget about versa -- then I won't have to '-nowidelut' to barely squeeze everything within 45k15:35
somlobtw, does the 36-bit BRAM thing have an 'off' switch I could try?15:36
daveshahThere isn't one as I wasn't expecting regressions, but you could try removing the "PDPW" sections from https://github.com/YosysHQ/yosys/blob/master/techlibs/ecp5/bram.txt15:42
tpbTitle: yosys/bram.txt at master · YosysHQ/yosys · GitHub (at github.com)15:42
daveshahOr, reverting https://github.com/YosysHQ/yosys/pull/1425 in its entirety15:42
tpbTitle: ecp5: Add support for mapping 36-bit wide PDP BRAMs by daveshah1 · Pull Request #1425 · YosysHQ/yosys · GitHub (at github.com)15:42
somlodaveshah: thanks, I'll give that a shot, and report back if I notice a difference...15:58
lolsbornPeople running diamond, are you doing so using LiteX on Windows or Linux?  I've had nothing but issues running it on Ubuntu, but I'm not sure what the cause is.15:59
daveshahI've used LiteX with Diamond on Linux without any problems16:01
daveshahWhat issues are you seeing? Does Diamond run alright on its own?16:01
lolsbornI can find the error, but basically it was running out of stack when running synth16:01
daveshahMight be a memory inference issue16:03
lolsbornI have only 8gb of ram on this machine, I don't know if that is enough, but the system wasn't showing it was memory constrained when running16:03
lolsbornThis is what the error looks like https://gist.github.com/lolsborn/1f54a68c23e3719d2e5d64d778f24c2b16:06
tpbTitle: diamond error · GitHub (at gist.github.com)16:06
*** CarlFK has quit IRC16:07
_florent_lolsborn: strange, are you building an example target from litex-boards? I'm also using Diamond on Linux without issues16:12
daveshahSeems like that error is coming from Tcl16:14
daveshahWhich is even odder16:14
daveshahThe only thing I can think of is Diamond version. I've only ever used 3.1016:14
lolsbornI haven't tried synthing other designs on this machine in diamond.  I'm just building the ulx3s target with picorv32.  Works perfectly with Trellis.16:15
lolsbornUsing Diamond 3.11.016:16
lolsbornI might just try reinstalling16:17
lolsborndaveshah: are you running Ubuntu?16:17
daveshahNo, Arch Linux16:17
lolsbornI had to unpack the rpm and run the install scripts manually16:18
daveshahI've previously run Diamond on Ubuntu 18.04 without issues too16:18
daveshahYep, I did the same16:18
lolsbornI'll try reinstalling16:19
daveshahI'd try 3.10 at the same time16:20
*** ambro718 has joined #litex16:21
lolsbornwill do16:30
lolsbornThis is where I'm at with diamond on ubuntu https://gist.github.com/lolsborn/53d956b6d22e13c590050fab89c2289c this seems to happen with 3.10 or 3.11 the command I am running is at the bottom18:20
tpbTitle: Issue with LiteX using diamond · GitHub (at gist.github.com)18:20
*** rohitksingh has joined #litex18:41
somlodaveshah: after reverting yosys PR 1425 (but keeping trellis and nextpnr at yesterday's latest), I'm still hovering in the 45-50MHz Fmax18:47
somlomaybe it's just that I've exhausted my quota of good luck earlier on, and now all the random seeds I end up with are balancing out the karma :)18:48
daveshahI can't see anything obvious on the nextpnr side that would be causing issues18:49
daveshahCould have been another Yosys change or just bad luck as you say18:50
*** rohitksingh has quit IRC18:50
somlook, I'll write it off to karma, keep spinning, while I work on migrating to the trellis board :)18:51
lolsbornlooks like this might be the issue I'm having https://electronics.stackexchange.com/questions/327527/lattice-icecube2-error-synplify-pro-32119:05
tpbTitle: fpga - Lattice iCEcube2, error synplify_pro 321 - Electrical Engineering Stack Exchange (at electronics.stackexchange.com)19:06
_florent_somlo: can you try to revert https://github.com/enjoy-digital/litex/commit/1425a68d9e68cd6af4508d4369512684d1b97138 and rebuild? that's the only change i can think of regarding litex during last month that could impact timings19:37
tpbTitle: wishbone2csr: refactor using FSM, reduce latency (make it asynchronou… · enjoy-digital/litex@1425a68 · GitHub (at github.com)19:37
somlo_florent_: I'll try that one next, thanks!19:55
*** CarlFK has joined #litex20:23
lolsbornI finally got Diamond working, man that was painful. The only thing I think could improve in LiteX is discovery of Diamond if --gateware-tool-path is not specified.  /opt/Diamond seems arbitrary since the rpm installs to /usr/local/diamond and if you create a symlink with a trailing / it breaks. The real issue on Ubuntu though is /bin/sh being a symlink to dash and breaking many of the scripts in diamond20:45
lolsbornfwiw 3.11 seems to work fine20:50
*** rohitksingh has joined #litex20:57
_florent_lolsborn: ok good for Diamond, i'll try to add automatic discovery soon20:57
lolsbornI may make a script that installs converts diamond rpm to deb, installs it and then changes all the scripts from sh to bash just because everyone in my office uses ubuntu/debian and I think it would be useful for other folks21:01
*** ambro718 has quit IRC21:29
*** rohitksingh has quit IRC22:07
*** rohitksingh has joined #litex22:26
*** CarlFK has quit IRC23:51

Generated by irclog2html.py 2.13.1 by Marius Gedminas - find it at mg.pov.lt!