-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Sprites all going to PSRAM despite setAttribute function #3576
Comments
What happens if you disable PSRAM via board manager? |
Ahh bugger, Hey, thanks for pointing that out.. They are too big to fit in SRAM... But if i change all of the spr1 spr2 and nestedSprites to 120 x 120 they both go into SRAM. And after this change if I enable PSRAM in the board manager, they both go into PSRAM. Ive also moved the tft.begin() up to the top of the setup. Any ideas? |
Hey, so i have an update. I've since found out that this works, but only for sprites under 45 x 45 pixels. Is there a way of making the allowed size for sprites using SRAM bigger? i have had SRAM successfully hold 2 sprites at 200 x 150 pixels without problem (after turning PSRAM: Enabe off in the IDE setup.
|
Hi,
I hope someone can help me.
I have been trying for a while to send certain sprites to SRAM and others to PSRAM on a ESP32 wrover and they are all going to PSRAM regardless of any combination of uncommented lines in my setup. The LCD displays the sprites perfectly fine.
programCode.zip
I have tried using different boards in the board manager :
ESP32 dev module
ESP32 wrover module
ESP32 wrover kit (all versions)
Im using:
arduino IDE version 2.3.3
TFT_eSPI version 2.5.43
SSD1963 TFT controller in 8 bit parallel
The pins in the User_Setup.h file are:
in this example im just tring to push some nested sprites to another sprite and then to the lcd. which works fine. but its going to the wrong RAM allocation.
see code below.
The output im getting is:
The text was updated successfully, but these errors were encountered: