electronic_eel has quit [Ping timeout: 258 seconds]
electronic_eel has joined #nmigen
<_whitenotifier-f>
[nmigen-boards] tdaede opened pull request #114: ulx3s: fix copy-paste error in GPIO mappings. - https://git.io/JUuRd
hitomi2508 has joined #nmigen
emeb_mac has quit [Quit: Leaving.]
chipmuenk has joined #nmigen
jaseg has quit [Ping timeout: 258 seconds]
chipmuenk1 has joined #nmigen
chipmuenk has quit [Ping timeout: 260 seconds]
chipmuenk1 is now known as chipmuenk
jaseg has joined #nmigen
zignig_ has joined #nmigen
zignig has quit [Ping timeout: 240 seconds]
attie has joined #nmigen
jeanthom has joined #nmigen
jeanthom has quit [Quit: Leaving]
jeanthom has joined #nmigen
sebinho has joined #nmigen
<sebinho>
Hi Everybody, I just started investigating the use of nmigen for one of our projects. My main question is regarding simulation. How does the simulator compares to Cocotb? I have been using Cocotb extensively and was very pleased with it. Thx for your help
ademski has joined #nmigen
<sebinho>
so basically we have a lot of existing VHDL code that I was simulating with cocotb. Now we are looking into nmigen as a new way to implement new modules. Is there an easy way to use existing VHDL source files together with nmigen and get simulation support?
<ademski>
whitquark is developing cxxsim backend which i suppose it is going to enable that. Currently i'm using nmigen-cocotb (https://github.com/andresdemski/nmigen-cocotb). It just support verilog sources but you can use yosys-ghdl pluging to convert sources.
<sebinho>
so if I understand correctly, the Yosys plugin would convert my VHDL into an intermediate format that can be used by nmigen for simulation?
<ademski>
I'm using the following comand to convert vhdl to verilog: "ghdl --ieee=synopsys --std=08 -fexplicit -O3 --work=work {vhdl_files} -e {toplevel}; write_verilog {output_file}"
<ademski>
After that, you can use nmigen-cocotb to simulate your sources.
<sebinho>
I see thx for the explanation. How do you guys compare cocotb and nmigen simulator in terms of features? Why would you stick to cocotb instead?
sebinho has quit [Ping timeout: 245 seconds]
sebinho has joined #nmigen
sebinho has quit [Ping timeout: 245 seconds]
sebinho has joined #nmigen
<sebinho>
For those who have VHDL files already, another solution is to use Icarus Verilog to convert the nmigen Verilog files to VHDL. Then you can use cocotb and GHDL to simulate a complete VHDL design. https://iverilog.fandom.com/wiki/Using_VHDL_Code_Generator
jjeanthom has joined #nmigen
<ademski>
I didn't know that, thanks!
<vup>
I think daveshah has also used cxxrtl (basically the backend of cxxsim) to simulate verilog together with vhdl, so you don't necessarily have to convert your files
jeanthom has quit [Ping timeout: 256 seconds]
<ademski>
cocot vs nmigen-pysim ... I have a lot of simulation drivers in cocotb, that is why im stick to cocotb.
<sebinho>
@vup daveshah indeed I did read something about cxxrtl. In that case I suppose the simulation will be in C++?
<vup>
sebinho: if you use cxxrtl directly yes, however cxxsim is a way to use it from python with the same API as the nmigen python simulator (pysim)
<sebinho>
vup: is there any example available on how to use cxxsim?
Asu has joined #nmigen
<vup>
not sure, its still in development, you can check out the cxxsim branch of nmigen and then specify `engine="cxxsim"` in the constructor of `Simulator` I think
jjeanthom has quit [Ping timeout: 272 seconds]
jjeanthom has joined #nmigen
<sebinho>
yup: thx! I will check it out
<sebinho>
vup
sebinho has quit [Ping timeout: 245 seconds]
hitomi2508 has quit [Quit: Nettalk6 - www.ntalk.de]
emeb has joined #nmigen
<_whitenotifier-f>
[nmigen/nmigen-boards] whitequark pushed 1 commit to master [+0/-0/±1] https://git.io/JUubX