forked from micropython/micropython
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block keyboard input during execution of boot.py
on non-usb boards
#9179
Labels
Milestone
Comments
This should also perhaps extend to It's pretty much the |
My intention is that workflows start after boot.py is run but I think you are right that UART starts earlier. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On usb boards it's not possible to interfere with
boot.py
since usb doesn't start up that early.However on non-usb boards it's very much possible to do so.
This however makes it possible for serial noise (from plugging the board in) to send a KeyboardInterrupt and stop it.
I think it would eventually be a good idea to outright block all input while
boot.py
is running.The text was updated successfully, but these errors were encountered: