我已经将软件监控器的运行模式设置为非调试模式。然而，当我设置一个用于调试的断点并长时间停留时，软件仍然触发了重启。为什么会发生这种情况？
Hello,
我已经将软件监控器的运行模式设置为非调试模式。然而，当我设置一个用于调试的断点并长时间停留时，软件仍然触发了重启。为什么会发生这种情
I have set the software monitor's running mode to non-debugging mode. However, when I set a breakpoint for debugging and stay there for a long time, the software still triggers a restart. Why does this happen?
I am not sure how to understand this.
So SWT is triggering reset in debug mode? By default SWT is disable by debuggers in debug mode.
Is the timeout for reset corresponding with SWT timeout?
Also you can check the RGM FES register if the reset comes from SWT0 after reset.
Usually it is needed to perform at least one instruction execution when SWT0 expires so the device can take action on timeout.
Best regards,
Peter
Hello,
我已经将软件监控器的运行模式设置为非调试模式。然而，当我设置一个用于调试的断点并长时间停留时，软件仍然触发了重启。为什么会发生这种情
I have set the software monitor's running mode to non-debugging mode. However, when I set a breakpoint for debugging and stay there for a long time, the software still triggers a restart. Why does this happen?
I am not sure how to understand this.
So SWT is triggering reset in debug mode? By default SWT is disable by debuggers in debug mode.
Is the timeout for reset corresponding with SWT timeout?
Also you can check the RGM FES register if the reset comes from SWT0 after reset.
Usually it is needed to perform at least one instruction execution when SWT0 expires so the device can take action on timeout.
Best regards,
Peter
