Saturday, 2020-11-28

*** tpb has joined #litex00:00
*** lf has quit IRC00:44
*** lf has joined #litex00:44
*** Degi has quit IRC01:48
*** Degi has joined #litex01:49
*** Dolu_ has quit IRC02:38
*** Bertl_oO is now known as Bertl_zZ05:54
*** _whitelogger has quit IRC06:39
*** _whitelogger has joined #litex06:41
*** _whitelogger has quit IRC07:36
*** _whitelogger has joined #litex07:38
_florent_Finde: Ariane (CVA6 now: https://github.com/openhwgroup/cva6) would indeed be an interesting CPU to support, I've also been thinking about it, there will probably be opportunities to add support for it next year08:18
_florent_daveshah, somlo: not sure I followed exactly the issue you are looking at, but if you think it could be related to LiteX, happy to help (on monday)08:22
daveshahNo, it's definitely a synthesis bug08:23
_florent_ok, thanks08:24
*** _whitelogger has quit IRC08:33
*** _whitelogger has joined #litex08:35
daveshahgreat, I've reproduced the problem using litex_sim hacking the build script to run a Yosys opt pass09:45
daveshahnow I can compare the vcds and find exactly which signal is going wrong09:45
daveshahthere's no address bus activity at all with broken Yosys09:46
daveshahso something has definitely gone horribly, horribly wrong09:46
daveshahugh, I think the problem isn't actually in Yosys but some UB in Rocket/its glue (a debug register that is never clocked, reset or initialised now being validly optimised to x rather than 0)10:45
daveshahunfortunately, finding out where those clock/resets should be coming from is a bit tricky10:46
*** Dolu_ has joined #litex10:48
daveshahsomlo/_florent_: the following monkey-patch fixes the above UB by tying async reset to 1 so the FFs are kept at 0 instead of being undefined11:01
daveshahhttps://www.irccloud.com/pastebin/bVDYvlwo/11:02
tpbTitle: Snippet | IRCCloud (at www.irccloud.com)11:02
daveshahi'll leave it up to you as to whether this needs to be fixed by changing how the debug signals are tied in the LiteX Rocket glue, or whether there is a problem in Rocket itself11:02
daveshah(note that patch is for a minimal, not Linux, config but it was just about testing things as quickly as possible, I don't think it's the right fix anyway)11:03
daveshahnever mind, ignore that patch, I had some other stuff in my tree that was messing things up11:11
daveshahsomlo/_florent_: sorry for all the noise. ignore the previous diff, here is a proper patch that seems to work. https://github.com/enjoy-digital/litex/pull/71311:18
*** Bertl_zZ is now known as Bertl12:41
somlodaveshah, _florent_: I merged 713, as it does indeed fix litex+rocket when using the new yosys13:14
somlodaveshah: thanks a ton for tracking this down!13:14
daveshahgreat, thanks for confirming!13:14
daveshahno problem13:14
*** Bertl is now known as Bertl_oO14:43
*** andrewb1999 has joined #litex15:49
*** kgugala_ has joined #litex16:12
*** kgugala has quit IRC16:15
*** kgugala has joined #litex16:16
*** kgugala_ has quit IRC16:19
*** kgugala_ has joined #litex16:30
*** kgugala has quit IRC16:33
*** nelgau has joined #litex20:33
*** cjearls has joined #litex23:09
cjearlsHi, I'm doing some Verilog digital design on Linux, and I was hoping that someone would be able to direct me to some good tools for waveform viewing and debugging. For a while, I have been using ModelSim in a Windows VM, but I'd prefer all my tools to run natively on Linux. I tried using Verilator to dump waveforms, then GTKWave to view them, but it didn't seem as easy to use as Modelsim. Do you have any recommendations for a good combination23:13
cjearlsof tools?23:13

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