d_olex has quit [Remote host closed the connection]
d_olex has joined #amaranth-lang
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 264 seconds]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 256 seconds]
frgo has joined #amaranth-lang
frgo has quit [Ping timeout: 255 seconds]
frgo has joined #amaranth-lang
frgo has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
frgo has quit [Remote host closed the connection]
frgo has joined #amaranth-lang
frgo_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo_ has quit [Ping timeout: 264 seconds]
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
Hoernchen has joined #amaranth-lang
galibert[m] has quit [Quit: Idle timeout reached: 172800s]
frgo_ has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo_ has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
frgo_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
<Hoernchen>
is there a pretty way to abuse amaranth to generate verilog testbenches? i'm using a clarity designer generated mac Instance("foo",..), so pure python sim doesn't work, so i tried the opposite approach by going for all verilog using verilog.convert_fragment which works fine as long as there are ports, but.. my tb does not/should not have ports..
<whitequark[cis]>
what do you expect to be in a generated testbench?
<_whitenotifier-9>
[amaranth] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-1401-af4e4a748950e3ab8d144ec56bf066449a524c46 - https://github.com/amaranth-lang/amaranth
<Hoernchen>
just basic sync stuff, nothing fancy, that drives the dut +- maybe one initial statement for dumpvars
<whitequark[cis]>
amaranth won't generate a behavioral testbench for you
<whitequark[cis]>
so no $dumpvars, no $finish, nothing like that
<whitequark[cis]>
you could of course write some RTL to drive another design, just like you'd do it for synthesis
<Hoernchen>
yeah, i have settled for generating the not-tb and then wrapping that in a small python generated verilog template, and then uh.. driving all of that using cocotb..
<whitequark[cis]>
and then add a stub testbench that drives a clock, does $finish and so on
<whitequark[cis]>
yeah. so for the next release we plan to add CXXRTL support, which will let you simulate instances
<_whitenotifier-9>
[amaranth-lang/amaranth-lang.github.io] github-merge-queue[bot] 3ff1eba - Deploying to main from @ amaranth-lang/amaranth@0915b9a043f8c8c6511a8e398948d93b82f92bbf 🚀
<Hoernchen>
mmh yes, cxxrtl was the other idea i had: what if i compile my generated verilog and then load that somehow...
<whitequark[cis]>
the cxxsim branch does exactly that
<Hoernchen>
oooh
<whitequark[cis]>
but it's rather unfinished and very "when it breaks you get to keep all the parts"
esden[m] has quit [Quit: Idle timeout reached: 172800s]