whitequark[cis] changed the topic of #amaranth-lang to: Amaranth hardware definition language · weekly meetings: Amaranth each Mon 1700 UTC, Amaranth SoC each Fri 1700 UTC · play https://amaranth-lang.org/play/ · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
Degi has quit [Ping timeout: 260 seconds]
Degi has joined #amaranth-lang
Guest57 has joined #amaranth-lang
Guest57 has quit [Client Quit]
weshu has joined #amaranth-lang
Psentee has quit [Ping timeout: 276 seconds]
Ekho has quit [Ping timeout: 246 seconds]
tpw_rules has quit [Ping timeout: 246 seconds]
Psentee has joined #amaranth-lang
tpw_rules has joined #amaranth-lang
Ekho- has joined #amaranth-lang
frgo_ has quit [Read error: Connection reset by peer]
frgo has joined #amaranth-lang
weshu has quit [Ping timeout: 240 seconds]
cyrozap has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
cyrozap has joined #amaranth-lang
V has quit [Remote host closed the connection]
V has joined #amaranth-lang
__DuBPiRaTe__ has joined #amaranth-lang
urja has quit [Read error: Connection reset by peer]
urja has joined #amaranth-lang
SjefCoder has joined #amaranth-lang
<SjefCoder> If you drive a clockdomain through a combinatorial statement: my.domain.clk.eq(self.clkout), how can you still use the simulator's add_clock? because now I get the error: "amaranth.hdl._ir.DriverConflict: Clock signal is already driven by combinational logic"
<whitequark[cis]> you can't
<whitequark[cis]> drive self.clkout instead
<SjefCoder> got it
<SjefCoder> I need to then artificially create pulses via testbench?
<SjefCoder> I mean manually toggle the pin on and off for a certain period?
<whitequark[cis]> yes
<whitequark[cis]> that is what add_clock does internally
SjefCoder has quit [Quit: Client closed]