You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the code runs, the display is visible. However, copying a file to CIRCUITPY causes the display to blank. It seems the display is not outputting anything at all (not correct sync), because my HDMI to USB video capture dongle shows a test pattern during this time. After the write finishes, the display comes back.
Description
This happens back to 9.2.0, and both on a Feather RP2350 with self-soldered PSRAM and on a Metro RP2350 prototype. Encountered while working on #10028 but is not caused by the method that PR uses to set up the display.
Additional information
No response
The text was updated successfully, but these errors were encountered:
It looks like picodvi on rp2350 uses an IRQ on core0 to start the frame via irq_set_exclusive_handler(DMA_IRQ_1, dma_irq_handler); in common_hal_picodvi_framebuffer_construct which is running in core0. So, it's expected that flash writing blocks this irq. we'd need to place the irq handler on core1 for this to work. or else not fully block this specific interrupt during flash writes, as it should be safe.
CircuitPython version and board name
Code/REPL
Behavior
After the code runs, the display is visible. However, copying a file to CIRCUITPY causes the display to blank. It seems the display is not outputting anything at all (not correct sync), because my HDMI to USB video capture dongle shows a test pattern during this time. After the write finishes, the display comes back.
Description
This happens back to 9.2.0, and both on a Feather RP2350 with self-soldered PSRAM and on a Metro RP2350 prototype. Encountered while working on #10028 but is not caused by the method that PR uses to set up the display.
Additional information
No response
The text was updated successfully, but these errors were encountered: