20:47 <d1b2> <sarea> I'm not quite sure but what is the best way to reset a custom ClockDomain (and all its assigned signals)? for example when I re-run my example applet via the CLI.

20:49 <d1b2> <dragonmux> by using that clock domain's ResetSignal().eq(1) to manually pulse the domain's resets

21:03 <d1b2> <sarea> hmmm... ok, but is there any exact condition that tells me when ResetSignal.eq(1) should be used? I just noticed that on the sync domain all signals are automatically reset after every start of my applet, while on a custom clockdomain this is not; the goal would be to get exactly the same behavior for my custom domain

21:17 <d1b2> <Attie> are you looking for the logic in your custom domain to be reset, or for the clock specifically?... (i.e: perhaps gated / in phase at start)

21:18 <d1b2> <Attie> I believe the former should be taken care of by the glasgow infrastructure...

21:18 <d1b2> <Attie> try referencing the VGA applet for example, make sure you set up the clock domain in the same way

21:19 <d1b2> <Attie> (if you don't, iirc it is possible to get a "running" applet without the reset connected to some parts, so it'll misbehave on re-run)

21:32 <d1b2> <sarea> actually i just want to reset a counter when restarting the app that is on the custom domain; here is an example:

21:33 <d1b2> <sarea> m.domains.ext = cd_ext = ClockDomain('ext') m.d.comb += cd_ext.clk.eq(self.bus.clk_signal_i) with m.If(counter != 0): m.d.ext += counter.eq(counter-1) with m.Else(): m.d.ext += self.bus.io_o.eq(1)

21:34 <d1b2> <sarea> I would have thought that this would be automatically reset on re-run