-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
Improve lvgl memory #676
Comments
Try increasing |
I ever used https://nightly.openhasp.com/ precompiled 0.7 FOR SUNTO 7": STEP COMPILING:
|
Where do i found source 0.7? |
It is here: https://github.com/HASwitchPlate/openHASP For Gitpod use https://gitpod.io/new/#https://github.com/HASwitchPlate/openHASP/tree/master |
i cant found 0.7, i need for sutun 7 inch |
What do u choose for sunton 7 inch : extra_default_envs = And what file define 👍 LV_MEM_CUSTOM.??? |
COMPILING STEP Click platformio_override.ini to open it, and to select your firmware flavour for your hardware uncomment in the extra_configs section the platform of your hadware, for example for ESP32: STEP1 If you use customization, remove the comment from the line -DUSE_CONFIG_OVERRIDE and make sure you have your own user_config_override.h in place: STEP2 And finally select your supported hardware from the extra_default_envs section by uncommenting the corresponding line. For example to build firmware for Lanbon L8, you should remove that comment only: STEP3 Save the file by pressing Ctrl + S or selecting Save from the top-left menu. Note STEP 4 Customization STEP 5 Parameters lvgl is in file : include\user_config_override-template.h row 150 define LV_MEM_SIZE (64 * 1024U) // 64Kb on ESP32 with PSram |
The problen is rename: include\user_config_override-template.h to include\user_config_override.h NOW where can found : STEP 5 Parameters lvgl is in file : include\user_config_override-template.h row 150 define LV_MEM_SIZE (64 * 1024U) // 64Kb on ESP32 with PSram |
i use : define LV_MEM_SIZE (64 * 1024U) BEFORE
AFTER Device MemoryFree Heap | 75.34 KiB LVGL Memory free lgvl INCREASE 5Kib |
is it better use define LV_MEM_CUSTOM 1 ? |
I don't think that's a good idea for you, you would have to programme your own memory management. |
When you start customizing the firmware, it is up to you to test it and tweak where needed. |
Di u have same guide for improve this mem allocaror? |
Just change |
so i do |
Just created a PR that will allow avoiding to have to modify Not that LV_MEM_CUSTOM 1 is really recommended: To be tested. It made my sc01plus lose WiFi randomly. edit: the PR is accepted. One no longer needs to modify |
You'll need to keep an eye on the memory fragmentation on the info page. |
I've used this method too to overcome an issue with both the Sunton and Guition screen crashing due to lack of available LVGL memory. Forgive my ignorance here (my first program was input via paper tape on an acoustic coupler telephone line) but with these higher resolution screens would it be possible for the default LVGL allocation to be higher? I am not able to create as many screens or use as many objects as I do on my Lanbon screens without having to do a custom compile. |
What settings did you change? Were there any adverse effects? I can't know what number of pages and objects are being used by everybody, so your feedback is needed to come up with a reasonable default value. The current default have been in place for quite a while and are quite stable. We can increase the LVGL memory, but the change needs to be justified and stable. What limit do you suggest? |
No suggestions? |
Sorry been travelling again. I changed LV_MEM_CUSTOM 1 as noted in a previous thread. So far no noticeable problems in the past 3 weeks. Fragmentation had increased to 70%. I just rebooted one of the panels and fragmentation now 45%. I'll add notes if anything changes/goes wrong! |
i use Sunton ESP32-S3 7" 800*480
Device Memory
Free Heap | 65.80 KiB
Free Block | 55.98 KiB
Fragmentation | 14%
PSRam Free | 7.18 MiB
PSRam Size | 7.99 MiB
Total | 64.00 KiB
Free | 5.61 KiB
Fragmentation | 14%
out of memory ..... block screen...
solution reflash firmware ...
The text was updated successfully, but these errors were encountered: