11:05 <key2> if yes, then how do you manage the m.next = "xxx" ?

11:05 <key2> to which FSM would it apply

11:07 <d1b2> <dragonmux> the with blocks scope the FSMs, so the m.next applies to the FSM it's directly inside of

14:09 <key2> so how would you do in this case in the 2nd FSM to say you want to change the state of the first FSM ? if both would be written with m.next = "xxx" without refering to the FSM

14:09 <bl0x_> dragonmux: is there then a way to refer to the outer m.next from the inner FSM?

14:09 <bl0x_> Oops, same question ^^

14:09 <key2> yep

14:09 <key2> :)

14:10 <bl0x_> You can name the FSM in the with statement. Maybe that helps to differentiate?

14:12 <d1b2> <dragonmux> the easiest way that makes sense to have the inner FSM cause the outer to change state, is to have a signal that you m.d.comb to 1 that you have the case the inner is written in react on to change to a new state

14:12 <d1b2> <dragonmux> but tbqh, it's easier to write the two FSMs separately and have them "communicate" with a series of signals representing important conditions that cause them to chagnge states

14:12 <d1b2> <dragonmux> *change

18:57 <bl0x_> Yep, that's what I usually do. It's easier to read and to reason about. Also aren't nested FSM just a fancy way to express grouping of several states?