I made a change to the code that I think is going to reduce both RAM and FLASH use

[kdschlosser]

If there is anyone that is willing to test the code change I made it would be helpful. I made a change that should reduce the compiled binary size and I am hopeful that it might reduce the memory consumption for people using an esp32-s3

Let me know if there is change in the compiled bin size and if you could check the memory use to see what that looks like on an S3 that would be helpful.

[rzuehlsd]

Hi Kevin,

WOW, that was a quick reply. I fetched the current head and did a new build with the unchanged toml file. My little test program also worked.

Below is a comparison of old vs. new build. So it seems that your changes increased the app size by 2 kB but had no effect on PSIRAM.

I will be on a short vacation next week, so if you need additional testing I can do it on the next weekend.

Again thanks for your work.

Ralf

Old partition and memory sizes:

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2573904  (    2480 remaining)
total                  2639440

MCU Parameter:
CPU Freq:    240.0 MHz
Free RAM:    5697.06 kB
Flash:       16777.22 kB
MCU Temp:    27 C
Extended SPIRAM is supported!

Virtual File System Usage:
Total space: 14135.3 kB
Free space:  14118.91 kB ( 99.88409 %)

New partition and memory sizes:

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2575904  (     480 remaining)
total                  2641440


MCU Parameter:
CPU Freq:    240.0 MHz
Free RAM:    5697.06 kB
Flash:       16777.22 kB
MCU Temp:    30 C
Extended SPIRAM is supported!

Virtual File System Usage:
Total space: 14135.3 kB
Free space:  14118.91 kB ( 99.88409 %)
`` 

[kdschlosser]

hmmm.... strange that the binary size is larger...

I wonder something...

Add the following to your build command and see if it makes any difference. you will need to compile old and also the new to test with using these additional build commands.

Try it this way for both new and old
CONFIG_COMPILER_OPTIMIZATION_SIZE=y CONFIG_COMPILER_OPTIMIZATION_PERF=n

and then try it this way both new and old.
CONFIG_COMPILER_OPTIMIZATION_SIZE=n CONFIG_COMPILER_OPTIMIZATION_PERF=y

[rzuehlsd]

I will try that out once i am back from my HolidaysVon meinem iPhone gesendetAm 19.07.2025 um 16:39 schrieb Kevin Schlosser ***@***.***>: hmmm.... strange that the binary size is larger... I wonder something... Add the following to your build command and see if it makes any difference. you will need to compile old and also the new to test with using these additional build commands. Try it this way for both new and old CONFIG_COMPILER_OPTIMIZATION_SIZE=y CONFIG_COMPILER_OPTIMIZATION_PERF=n and then try it this way both new and old. CONFIG_COMPILER_OPTIMIZATION_SIZE=n CONFIG_COMPILER_OPTIMIZATION_PERF=y —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[kdschlosser]

I am working on a very large modification that is going to flatten the current API so it is like the LVGL C API. The whole class organization that currently exists will be done away with. The only classes that will exist are for structures in LVGL and if those structures have fields that are not private those will be accessible but no class will have any methods. they will all be module level function calls exactly like what is done in LVGL.

What I am trying to figure out is why this ESP-IDF config option CONFIG_SPIRAM_XIP_FROM_PSRAM=y ends up use 2mb of SPIRAM. It's like it's moving the entire firmware code into RAM and running it from there.

[rzuehlsd]

So, I am back and will try out your recommendations on my ESP32S3 FH16R8.

To me it seems that optimization for size yields about 250k more available RAM, but still not what is expected.

Here are the result with:

CONFIG_COMPILER_OPTIMIZATION_SIZE=y CONFIG_COMPILER_OPTIMIZATION_PERF=n

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2454544  (    3056 remaining)
total                  2520080

---------------------------------------------
MCU Parameter:
CPU Freq:    240.0 MHz
Free RAM:    5959.2 kB
Flash:       16777.22 kB
MCU Temp:    26 C
Extended SPIRAM is supported!

Virtual File System Usage:
Total space: 14254.08 kB
Free space:  14241.79 kB ( 99.9138 %)
---------------------------------------------

and now with:

CONFIG_COMPILER_OPTIMIZATION_SIZE=n CONFIG_COMPILER_OPTIMIZATION_PERF=y

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2600864  (      96 remaining)
total                  2666400

---------------------------------------------
MCU Parameter:
CPU Freq:    240.0 MHz
Free RAM:    5697.06 kB
Flash:       16777.22 kB
MCU Temp:    30 C
Extended SPIRAM is supported!

Virtual File System Usage:
Total space: 14110.72 kB
Free space:  14094.34 kB ( 99.88389 %)
---------------------------------------------

But after pulling the current head and compiling with the settings you recommended I get the following error message (excerpt):

[1484/2340] Building C object esp-idf/main/CMakeFiles/__idf_main.dir/__/__/lv_mp.c.obj                                                            
ninja: build stopped: subcommand failed.
ninja failed with exit code 1, output of the command is in the /Users/rz/Desktop/IDEs/esp/lvgl_micropython/lib/micropython/ports/esp32/build-ESP32_GENERIC_S3-SPIRAM_OCT/log/idf_py_stderr_output_92415 and /Users/rz/Desktop/IDEs/esp/lvgl_micropython/lib/micropython/ports/esp32/build-ESP32_GENERIC_S3-SPIRAM_OCT/log/idf_py_stdout_output_92415
-e See https://github.com/micropython/micropython/wiki/Build-Troubleshooting
make: *** [all] Error 1

Seems building i2c_bus.c has caused the error:

.c.obj -c /Users/rz/Desktop/IDEs/esp/lvgl_micropython/ext_mod/lcd_bus/esp32_src/i2c_bus.c
/Users/rz/Desktop/IDEs/esp/lvgl_micropython/ext_mod/lcd_bus/esp32_src/i2c_bus.c: In function 'i2c_init':
/Users/rz/Desktop/IDEs/esp/lvgl_micropython/ext_mod/lcd_bus/esp32_src/i2c_bus.c:151:5: error: 'ret' undeclared (first use in this function)
151 |     ret = esp_lcd_new_panel_io_i2c(self->port , &self->panel_io_config, &self->panel_io_handle.panel_io);

[kdschlosser]

OK the compile error should be fixed now...

I need to see a before and after using the same compile parameters.

Also add CONFIG_SPIRAM_XIP_FROM_PSRAM=n to the build command as well.

[rzuehlsd]

Just pulled the latest files and compiled with all combinations of recommended compile flags.
To me the results are somewhat disappointing.
May be some flags are excluding each other.

Opt_Size    Opt_Perf.      XIP_PSRAM       App Size   RAM Size
    N            N            N            2600416    5697 k
    N            N            Y            2600416    5697 k
    N            Y            N            2600416    5697 k
    N            Y            Y            2600416    5697 k
    Y            N            N            2454352    5959 k
    Y            N            Y            2454352    5959 k
    Y            Y            N            2600416    5697 k
    Y            Y            Y            2600416    5697 k
``
So only the size optimization yields a higher RAM size, all other combinations make no difference.

I also realized that my lvgl test program ist not running anymore as the display driver could not be imported.

Hope this gives you a few hints. 

Kind regards

Ralf

[kdschlosser]

another thing is you can only specify size or performance, not both.

[kdschlosser]

I also just updated the code again which might have been causing config parameters to not work properly.

[kdschlosser]

This is what the ESP-IDF does internally with the CONFIG_COMPILER_OPTIMIZATION_SIZE and CONFIG_COMPILER_OPTIMIZATION_PERF config options..

If you set the following..
CONFIG_COMPILER_OPTIMIZATION_SIZE=y
CONFIG_COMPILER_OPTIMIZATION_PERF=y

then the ESP-IDF sets them as
CONFIG_COMPILER_OPTIMIZATION_SIZE=n
CONFIG_COMPILER_OPTIMIZATION_PERF=y

if you have the config options set to
CONFIG_COMPILER_OPTIMIZATION_SIZE=n
CONFIG_COMPILER_OPTIMIZATION_PERF=n

then the ESP-IDF sets them to
CONFIG_COMPILER_OPTIMIZATION_SIZE=n
CONFIG_COMPILER_OPTIMIZATION_PERF=y

if they are set to
CONFIG_COMPILER_OPTIMIZATION_SIZE=y
CONFIG_COMPILER_OPTIMIZATION_PERF=n

or they are set to
CONFIG_COMPILER_OPTIMIZATION_SIZE=n
CONFIG_COMPILER_OPTIMIZATION_PERF=y

then the ESP-IDF leaves them alone.

[kdschlosser]

the CONFIG_SPIRAM_XIP_FROM_PSRAM option only works on the ESP32-S3 and the ESP32-P4

[rzuehlsd]

So new try:

I have an ESP32-S3 with 4MB Flash and 2 PSRAM as well as with 16M Flash and 8MB PSRAM. First I try with the FH18R8 version.

So below are my results from the different compilation. So to me it looks very strange. The compilation flags with the exception of size optimizations seem to have no effect on available RAM size. May be there is something wrong with my build command?

My Build command: 
 python3 make.py esp32 BOARD=ESP32_GENERIC_S3 BOARD_VARIANT=SPIRAM_OCT --flash-size=16 DISPLAY=rgb_display INDEV=gt911 CONFIG_FREERTOS_HZ=1000 CONFIG_ESP_DEFAULT_CPU_FREQ_MHZ_240=y CONFIG_ESPTOOLPY_FLASHMODE_QIO=y CONFIG_ESPTOOLPY_FLASHFREQ_120M=y CONFIG_IDF_EXPERIMENTAL_FEATURES=y CONFIG_SPIRAM_SPEED_120M=y CONFIG_SPIRAM_FETCH_INSTRUCTIONS=y CONFIG_SPIRAM_RODATA=y CONFIG_ESP32S3_DATA_CACHE_LINE_64B=y CONFIG_COMPILER_OPTIMIZATION_SIZE=n CONFIG_COMPILER_OPTIMIZATION_PERF=y 
CONFIG_SPIRAM_XIP_FROM_PSRAM=y

Below are the results from my build with different compile flags.

Size Optimization:

CONFIG_COMPILER_OPTIMIZATION_SIZE=y
CONFIG_COMPILER_OPTIMIZATION_PERF=n
CONFIG_SPIRAM_XIP_FROM_PSRAM=n

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2454448  (    3152 remaining)
total                  2519984

Free RAM:    5959.2 kB
Flash:       16777.22 kB

Size Optimization and ...XIP_FROM_PSRAM:

CONFIG_COMPILER_OPTIMIZATION_SIZE=y
CONFIG_COMPILER_OPTIMIZATION_PERF=n
CONFIG_SPIRAM_XIP_FROM_PSRAM=y

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2454448  (    3152 remaining)
total                  2519984

Free RAM:    5959.2 kB
Flash:       16777.22 kB

Now with performance optimizations:

CONFIG_COMPILER_OPTIMIZATION_SIZE=n
CONFIG_COMPILER_OPTIMIZATION_PERF=y
CONFIG_SPIRAM_XIP_FROM_PSRAM=n

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2600512  (     448 remaining)
total                  2666048

Free RAM:    5959.2 kB
Flash:       16777.22 kB

Performance optimization and ...XIP_FROM_PSRAM:

CONFIG_COMPILER_OPTIMIZATION_SIZE=n
CONFIG_COMPILER_OPTIMIZATION_PERF=y
CONFIG_SPIRAM_XIP_FROM_PSRAM=y

bootloader  @0x000000    19152  (   13616 remaining)
partitions  @0x008000     3072  (    1024 remaining)
application @0x010000  2600512  (     448 remaining)
total                  2666048

Free RAM:    5959.2 kB
Flash:       16777.22 kB

[rzuehlsd]

The other problem I discovered is that my test program does not work any more as there is no display driver available. Here is my test program which work two pulls earlier.

I get the following error:

import test
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "test.py", line 2, in <module>
ImportError: no module named 'display'

and here is the program:

import lvgl as lv
import display

# Set display rotation (orientation)
# Options: lv.DISPLAY_ROTATION._0, _90, _180, _270
disp = lv.display_get_default()
disp.set_rotation(lv.DISPLAY_ROTATION._90)  # Rotate 90 degrees (portrait to landscape)

# Create a screen with red background
scr = lv.obj()
scr.set_style_bg_color(lv.color_hex(0xFF0000), 0)  # Red background
scr.set_style_bg_opa(lv.OPA.COVER, 0)

# Create a button with a label
btn = lv.button(scr)
btn.align(lv.ALIGN.CENTER, 0, -50)  # Move button up
btn.set_size(150, 50)
label = lv.label(btn)
label.set_text('Hello World!')
label.center()

# Create a text area (text entry section)
textarea = lv.textarea(scr)
textarea.set_size(300, 80)
textarea.align(lv.ALIGN.CENTER, 0, 50)  # Position below button
textarea.set_placeholder_text("Enter text here...")
textarea.set_one_line(False)  # Allow multiple lines

# Create a keyboard for text input
kb = lv.keyboard(scr)
kb.set_size(400, 200)
kb.align(lv.ALIGN.BOTTOM_MID, 0, 0)
kb.set_textarea(textarea)  # Link keyboard to textarea

lv.screen_load(scr)

[kdschlosser]

OK that file is ONLY available if you use the toml build command. The data in the toml file is what constructs the display.py file that gets baked into the firmware. so if you don't use that feature there is no display.py file. I added that feature for folks that wanted a way to get up and running as easy as possible where they wouldn't have to deal with getting the display and touch drivers set up and they can focus only on the UI code.

[kdschlosser]

The toml build command also handles all options that need to be passed to the compiler so any additional build commands you add simply get ignored.