Wednesday, 2021-04-07

*** revolve <revolve!> has quit IRC02:40
*** revolve <revolve!> has joined #libre-soc02:42
*** lkcl <lkcl!> has quit IRC03:25
*** lkcl <lkcl!> has joined #libre-soc03:39
*** lkcl <lkcl!> has quit IRC05:08
*** lkcl <lkcl!> has joined #libre-soc05:21
*** Ericounet <Ericounet!~Eric@2a01:e0a:d0:3c20:a60a:ec27:ee23:d280> has joined #libre-soc06:27
*** raster <raster!~raster@enlightenment/developer/raster> has joined #libre-soc08:44
*** revolve <revolve!> has quit IRC09:10
*** revolve <revolve!> has joined #libre-soc09:12
*** programmerjake <programmerjake!programmer@gateway/shell/> has quit IRC09:50
*** programmerjake <programmerjake!programmer@gateway/shell/> has joined #libre-soc10:07
*** Ericounet <Ericounet!~Eric@2a01:e0a:d0:3c20:a60a:ec27:ee23:d280> has quit IRC11:05
*** Ericounet <Ericounet!~Eric@2a01:e0a:d0:3c20:2617:18f9:538e:2e8e> has joined #libre-soc13:22
lkclChips4Makers: very frustrating - enabling clock (run=True) causes a lock-up in both verilator *and* iverilog if allowed to run to the point where clock ticks not under reset14:32
lkclhowever running under *litex* with verilator works perfectly well14:32
lkclno lockup whatsoever14:32
lkclhowever if i use verilator v4.106 there is *no* lockup14:35
lkclhowever all output signals are zero14:35
lkclall vcd trace signals are also zero14:35
Chips4Makerslkcl: OK, now I think of it, it may be because that the clock is defined in cocotb and not in verilog leading to a lot of round trips between python and iverilog.14:37
lkclahh ok14:48
lkclso... that would involve writing a "manual" clock generator of some kind, in verilog?  sys_clk = ~sys_clk or something?14:50
lkclor a c++ module of some kind?14:51
lkclin litex there is a module called "clocker", i will look it up14:51
lkclis there an easy way in cocotb to run external clocks?14:58
Chips4MakersIn Verilog/VHDL would be OK I think.15:15
*** revolve <revolve!> has quit IRC15:40
*** revolve <revolve!> has joined #libre-soc15:45
lkcldeep breath: it's going to need special modification of cocotb to be able to run a special thread that runs sys_clk independently16:29
lkclwhich will require pthread mutexes around parts of cocotb/share/lib/verilator/verilator.cpp16:31
Chips4MakersCan't you just hack in verilog code in top level ?16:37
lkclChips4Makers, using which signal to drive the clock?16:40
lkclthere has to be a clock... to drive the clock16:40
Chips4MakersI'm not sure about verilog, you should be able to use #n to execute something after a certain amount of time. In VHDL it would be 'clk <= ~clk after 10ns;'16:43
lkclahh yeah that would do it17:01
lkclverilator: always #xxx is unsupported17:15
lkcli'm tempted to suggest using cxxsim.17:17
lkclit can do mixed VHDL, verilog and ilang,17:18
lkclit's not really cosimulation because it's just "converting everything to c++"17:18
lkcland i already have some JTAG test benches (assuming a general JTAG interface)17:22
*** Ericounet <Ericounet!~Eric@2a01:e0a:d0:3c20:2617:18f9:538e:2e8e> has quit IRC17:43
*** omoiti <omoiti!~omoiti@> has joined #libre-soc18:29
Chips4Makerscxxsim is mainly WIP and can't be used from cocotb AFAIK.18:54
Chips4MakersMost of the questions on nmigen channel are answered by whitequark that it is a feature planned for the future...18:56
*** omoiti <omoiti!~omoiti@> has quit IRC19:53
lkclChips4Makers, yes i took a look again at it - i thought there'd been much more progress20:25
*** omoiti <omoiti!~omoiti@> has joined #libre-soc20:50
lkclmeeting 20mins lxo programmerjake cesar[m]121:39
*** omoiti <omoiti!~omoiti@> has quit IRC22:06
*** revolve <revolve!> has quit IRC22:10
*** revolve <revolve!> has joined #libre-soc22:12
*** omoiti <omoiti!~omoiti@> has joined #libre-soc22:22
*** omoiti <omoiti!~omoiti@> has quit IRC23:18

Generated by 2.17.1 by Marius Gedminas - find it at!