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
I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
General issue report
Hi,
We found that the LCD display screen may be corrupted (see link below) if Wi-Fi is connected and has some activities (e.g. communicating with host, performing OTA update, etc). If Wi-Fi is turned off, the display works fine. Besides, the LCD display buffer is placed in the PSRAM (Octal mode@80MHz). If we temporarily change it to internal RAM, it seems the problem can be avoided.
github-actionsbot
changed the title
LCD display corruption caused by Wi-Fi activities
LCD display corruption caused by Wi-Fi activities (IDFGH-11174)
Oct 3, 2023
I have a similar issue. I made changes to the config as you mention here but it didnt work. Did you make any progress with this? Is there a way of switching PSRAM off for Wi-Fi while having PSRAM on for the LCD.
Answers checklist.
General issue report
Hi,
We found that the LCD display screen may be corrupted (see link below) if Wi-Fi is connected and has some activities (e.g. communicating with host, performing OTA update, etc). If Wi-Fi is turned off, the display works fine. Besides, the LCD display buffer is placed in the PSRAM (Octal mode@80MHz). If we temporarily change it to internal RAM, it seems the problem can be avoided.
https://drive.google.com/file/d/1J46mps4F4HuG6tB0qJbvmQMnisdy4Jf3/view?usp=sharing
Here is the IDF information:
IDF version: v4.4.4 (patched with commit "3cec3a00260")
LVGL version: v7.11
Display Buffer: PSRAM (Octal Mode@80MHz)
ESP LCD I/F: i80 bus, 8-bit bus width, 16-bit RGB, 10MHz pixel CLK
Can anyone help to see how to fix this issue or know the root cause?
Thanks for your help!
Gary
The text was updated successfully, but these errors were encountered: