Continuous execution of boot.py?

[speedbird620]

I have been struggling with the watchdog function a bit when I had an idea.

First "boot.py" will execute first and once it´s code has been executed, the "main.py" will start. Instead of enabling the built in watchdog function in "main.py", why not move the continuous executing code in "main.py" to "boot.py"? If the continuous code in "boot.py" will stop or fail to execute, "main.py" will execute which orders the microprocessor to reboot.

With this I can halt the code and connect with my editor without having to deal with the watchdog resetting the microprocessor after like 8 seconds.

Or am I missing something obvious?

[peterhinch]

If boot.py throws an exception, I don't think main.py gets to run. There is also the case where boot.py stalls - goes into an infinite loop or waits on a ridiculous delay...

[speedbird620]

Ok, thanks. Then I have to implement a hardware watch dog after all.