-
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
Hard fault with Feather RP2350 + ST7789 display after resizing terminal followed by running a REPL command #10084
Comments
I get the same hard fault with these additional firmware versions:
|
Also, it's not necessary to wire up the display just to reproduce the fault:
|
Another data point (thanks to @ Neradoc on discord for mentioning this): If you register a release_displays atexit, like this:
it stops the hard fault when you use the REPL. But, if your goal was to continue using the 2x zoom after code.py ends so you can have it for the REPL (perhaps with USB keyboard), then releasing the display doesn't help. |
The I think you want a |
Yeah... I figured something might be going out of scope, but the hard fault message said to file an issue, so I did.
Is that a thing that's possible? I didn't find any mention of such things in the docs. |
oh... actually... I just realized that the latest vs stable Environment variable docs are different, and I was looking at stable. Will CIRCUITPY_DISPLAY_WIDTH and CIRCUITPY_DISPLAY_HEIGHT work on something that's not a picodvi display? The latest docs page implies perhaps not? |
CircuitPython version and board name
Code/REPL
Behavior
1+1
,print("hello world")
, orimport board
, the board resets. The only exception I found is if I press Enter on a blank line. In that case, I get another>>>
prompt. A single space, a#
, or anything else I tried would trigger a reset.Description
Hardware setup:
Libraries:
Notes on Reproducer Code:
supervisor.reset_terminal(160, 120)
without changing anything about the root group, the display shows 4 tiled copies of the 160, 120 terminal. But, the characters look kinda glitched. It seems possible there might be some kind of buffer overflow thing going on.Additional information
No response
The text was updated successfully, but these errors were encountered: