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
Run the screen and the SD card simultaneously on one SPI
Version
latest stable Release (if not listed below)
IDE Name
Arduino IDE
Operating System
Windows 10
Flash frequency
80MHz
PSRAM enabled
yes
Upload speed
115200
Description
The underlying SD interface calls are all non-locking. Running both the screen and the SD card on the same SPI bus can only be managed with mutex-like operations at the upper program level. However, doing so at the upper level causes the screen to freeze when reading or writing to the SD card. Will this be optimized in the future? This is because SD mainly uses official libraries, and if locks are not provided, controlling this at the upper level is not very user-friendly.
Actually this is not true. The sd* functions are not directly called. Start looking after line 440 in sd_diskio.cpp to see the actual functions being called and where does the locking actually happen. There is something else going on on your end and if you want us to have a further look, please provide a minimal compilable example to reproduce
Board
ESP32-S3
Device Description
ESP32 series products
Hardware Configuration
Run the screen and the SD card simultaneously on one SPI
Version
latest stable Release (if not listed below)
IDE Name
Arduino IDE
Operating System
Windows 10
Flash frequency
80MHz
PSRAM enabled
yes
Upload speed
115200
Description
The underlying SD interface calls are all non-locking. Running both the screen and the SD card on the same SPI bus can only be managed with mutex-like operations at the upper program level. However, doing so at the upper level causes the screen to freeze when reading or writing to the SD card. Will this be optimized in the future? This is because SD mainly uses official libraries, and if locks are not provided, controlling this at the upper level is not very user-friendly.
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: