-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
displayio: the display does not survive a VM restart on SAMD21 #6277
Comments
With more testing, I noticed that sometimes, randomly, I can get a line or two of the traceback, before the display freezes, so there is some kind of race condition in there perhaps? |
A much easier reproducer: the HalloWing M0 Express display no longer works with recent versions of CircuitPython. |
The last version that works is |
Further testing leads me to believe that it's commit f0859ac that broke this. |
I have tried to experiment with this, but I really don't know what is happening. Perhaps the clock that the SPI peripheral uses gets shut down? The code itself doesn't refer to anything directly related to displayio. I give up. |
Confirmed via bisect. |
CircuitPython version
Code/REPL
Behavior
The display keeps displaying two squares and text even after the code finishes running.
It should instead display the REPL with the "Code done running." message.
Same happens when the code is interrupted with ctrl+c — instead of REPL, the display shows the last thing the program was displaying.
Description
The reverse happens if I copy-paste the display initialization code in the REPL — the display works until ctrl+c is pressed.
Additional information
If the display is initialized in board.c as part of the startup, then it initializes properly, but never displays anything.
The text was updated successfully, but these errors were encountered: