In reply to Mohamed_TN:
In reply to dave_59:
thanks Dave, I’m killing my sequence because something wrong is detected (functionally) and I need to stop it, I’ve used seq.kill() and sequencer.stop_sequences() with both I got the same error message (with sequencer.stop_sequences() the simulator stuck), for the driver state how can I identify it?
Thanks,
I think it is always not a good idea to kill or stop a sequence. It looks like you are in the phase of developing sequences. If something goes wrong you should reduce the number of cyles you are running and then debugging the issue. Killing a sequence will never point you to the cause of the problem.