The map is blank after pressing the move key.

[Quency-D]

I'm trying to add an SD card to the HELTEC-V4 expansion box, which uses a three-wire SDIO.
I'm trying to use the map feature in MUI, but I've found that it only displays one page of the map. When I try to move around to see the surroundings, it shows a blank screen. I've already loaded a large area on my SD card, but it's still blank when I press up, down, left, or right. Can anyone help me figure out what the problem is?

This is a video demonstration: https://youtube.com/shorts/eOwmG7snG9k?feature=share.

[mverch67]

It looks like the images cache is too small. All displayed tiles must fit into the cache otherwise these must be permanently reloaded from sd.

Try setting:
-D LV_CACHE_DEF_SIZE=2097152

[Quency-D]

It looks like the images cache is too small. All displayed tiles must fit into the cache otherwise these must be permanently reloaded from sd.

Try setting: -D LV_CACHE_DEF_SIZE=2097152

Adding this variable doesn't improve the situation; it remains exactly the same.

[mverch67]

Adding this variable doesn't improve the situation; it remains exactly the same.

Where's your code located to take a look at? Maybe it's inserted in the wrong place.

Edit: also what is your value of RAM_SIZE? It (of course) must be way bigger than LV_CACHE_DEF_SIZE, otherwise LV_CACHE_DEF_SIZE cannot be allocated.

[Quency-D]

HI, @mverch67 , I submitted the modified code to https://github.com/Quency-D/device-ui/tree/v4-tft-sd.
Below is the modified configuration file.

[heltec_v4_base] 
extends = esp32s3_base
board = heltec_v4
board_check = true
board_build.partitions = default_16MB.csv
build_flags = 
  ${esp32s3_base.build_flags}
  -D HELTEC_V4
  -I variants/esp32s3/heltec_v4


[env:heltec-v4]
custom_meshtastic_hw_model = 110
custom_meshtastic_hw_model_slug = HELTEC_V4
custom_meshtastic_architecture = esp32-s3
custom_meshtastic_actively_supported = true
custom_meshtastic_support_level = 1
custom_meshtastic_display_name = Heltec V4
custom_meshtastic_images = heltec_v4.svg
custom_meshtastic_tags = Heltec
custom_meshtastic_requires_dfu = true
custom_meshtastic_partition_scheme = 16MB

extends = heltec_v4_base
build_flags = 
  ${heltec_v4_base.build_flags}
  -D HELTEC_V4_OLED
  -D USE_SSD1306 ; Heltec_v4 has an SSD1315 display (compatible with SSD1306 driver)
  -D LED_PIN=35
  -D RESET_OLED=21
  -D I2C_SDA=17
  -D I2C_SCL=18
  -D I2C_SDA1=4
  -D I2C_SCL1=3

[env:heltec-v4-tft]
custom_meshtastic_hw_model = 110
custom_meshtastic_hw_model_slug = HELTEC_V4
custom_meshtastic_architecture = esp32-s3
custom_meshtastic_actively_supported = true
custom_meshtastic_support_level = 1
custom_meshtastic_display_name = Heltec V4 TFT
custom_meshtastic_images = heltec_v4.svg
custom_meshtastic_tags = Heltec
custom_meshtastic_requires_dfu = true
custom_meshtastic_partition_scheme = 16MB

extends = heltec_v4_base
build_flags = 
  ${heltec_v4_base.build_flags} ;-Os
  -D HELTEC_V4_TFT
  ; -D I2C_SDA=4
  ; -D I2C_SCL=3
    ; bool setPins(int clk, int cmd, int d0);
    ; bool setPins(int clk, int cmd, int d0, int d1, int d2, int d3);
  ; -D HAS_SDCARD
  -D HAS_SD_MMC
  -D SDMMC_CLK=3
  -D SDMMC_CMD=4
  -D SDMMC_D0=6
  -D SCREEN_TOUCH_USE_I2C1
  -D I2C_SDA1=47
  -D I2C_SCL1=48
  -D PIN_BUTTON2=35
  ; -D PIN_BUZZER=6
  ; -D USE_PIN_BUZZER=PIN_BUZZER
  -D CONFIG_ARDUHAL_LOG_COLORS
  -D RADIOLIB_DEBUG_SPI=0
  -D RADIOLIB_DEBUG_PROTOCOL=0
  -D RADIOLIB_DEBUG_BASIC=0
  -D RADIOLIB_VERBOSE_ASSERT=0
  -D RADIOLIB_SPI_PARANOID=0
  -D CONFIG_DISABLE_HAL_LOCKS=1
  -D INPUTDRIVER_BUTTON_TYPE=0
  -D HAS_SCREEN=1
  -D HAS_TFT=1
  -D RAM_SIZE=1560
  -D LV_LVGL_H_INCLUDE_SIMPLE
  -D LV_CONF_INCLUDE_SIMPLE
  -D LV_COMP_CONF_INCLUDE_SIMPLE
  -D LV_USE_SYSMON=0
  -D LV_USE_PROFILER=0
  -D LV_USE_PERF_MONITOR=0
  -D LV_USE_MEM_MONITOR=0
  -D LV_USE_LOG=0
  -D LV_BUILD_TEST=0
  -D USE_LOG_DEBUG
  -D LOG_DEBUG_INC=\"DebugConfiguration.h\"
  -D USE_PACKET_API
  -D LGFX_DRIVER=LGFX_HELTEC_V4_TFT
  -D GFX_DRIVER_INC=\"graphics/LGFX/LGFX_HELTEC_V4_TFT.h\"
  -D VIEW_320x240
  -D MAP_FULL_REDRAW
  -D DISPLAY_SIZE=320x240 ; landscape mode
  -D LGFX_PIN_SCK=17
  -D LGFX_PIN_MOSI=33
  -D LGFX_PIN_DC=16
  -D LGFX_PIN_CS=15
  -D LGFX_PIN_BL=21
  -D LGFX_PIN_RST=18
  -D CUSTOM_TOUCH_DRIVER
  -D TOUCH_SDA_PIN=I2C_SDA1
  -D TOUCH_SCL_PIN=I2C_SCL1
  -D TOUCH_INT_PIN=-1  ;45
  -D TOUCH_RST_PIN=44
;base UI
  -D TFT_CS=LGFX_PIN_CS
  -D ST7789_CS=TFT_CS
  -D ST7789_RS=LGFX_PIN_DC
  -D ST7789_SDA=LGFX_PIN_MOSI 
  -D ST7789_SCK=LGFX_PIN_SCK
  -D ST7789_RESET=LGFX_PIN_RST
  -D ST7789_MISO=-1
  -D ST7789_BUSY=-1
  -D ST7789_BL=LGFX_PIN_BL
  -D ST7789_SPI_HOST=SPI3_HOST
  -D TFT_BL=ST7789_BL
  -D SPI_FREQUENCY=40000000
  -D SPI_READ_FREQUENCY=4000000
  -D TFT_HEIGHT=320
  -D TFT_WIDTH=240
  -D TFT_OFFSET_X=0
  -D TFT_OFFSET_Y=0
  -D TFT_OFFSET_ROTATION=0
  -D SCREEN_ROTATE
  -D SCREEN_TRANSITION_FRAMERATE=5
  -D BRIGHTNESS_DEFAULT=130 ; Medium Low Brightness
  -D HAS_TOUCHSCREEN=1
  -D TOUCH_I2C_PORT=0
  -D TOUCH_SLAVE_ADDRESS=0x2E
  -D SCREEN_TOUCH_INT=TOUCH_INT_PIN
  -D SCREEN_TOUCH_RST=TOUCH_RST_PIN

lib_deps = ${heltec_v4_base.lib_deps}
  ${device-ui_base.lib_deps}
  # renovate: datasource=custom.pio depName=LovyanGFX packageName=lovyan03/library/LovyanGFX
  lovyan03/LovyanGFX@1.2.0
  # renovate: datasource=git-refs depName=Quency-D_chsc6x packageName=https://github.com/Quency-D/chsc6x gitBranch=master
  https://github.com/Quency-D/chsc6x/archive/5cbead829d6b432a8d621ed1aafd4eb474fd4f27.zip
  ; TODO revert to official device-ui (when merged)
  # renovate: datasource=git-refs depName=Quency-D_device-ui packageName=https://github.com/Quency-D/device-ui gitBranch=heltec-v4-tft
  ; https://github.com/Quency-D/device-ui/archive/7c9870b8016641190b059bdd90fe16c1012a39eb.zip

[mverch67]

RAM_SIZE is too small; try to determine the largest possible free PSRAM block ( heap_caps_get_largest_free_block(MALLOC_CAP_SPIRAM) ) at program start and then set -DRAM_SIZE to that value

[Quency-D]

When is this data retrieved? At the beginning of main or at the beginning of lvgl?

RAM_SIZE is too small; try to determine the largest possible free PSRAM block ( heap_caps_get_largest_free_block(MALLOC_CAP_SPIRAM) ) at program start and then set -DRAM_SIZE to that value

[mverch67]

The allocation takes place at the beginning of lvgl, see here:
https://github.com/lvgl/lvgl/blob/ffff043daf83391f051f355810301346ff4e24eb/src/lv_init.c#L197

device-ui/include/lv_conf.h

Line 62 in 63967a4

#define LV_MEM_SIZE (RAM_SIZE * 1024U) /*[bytes]*/

[Quency-D]

Thank you for your patient explanation. I have currently adjusted RAM_SIZE to the maximum -D RAM_SIZE=1780, and the value obtained by heap_caps_get_largest_free_block(MALLOC_CAP_SPIRAM) is now 71668. However, the map is still surrounded by blank space, just like before. But after setting this macro -D LV_CACHE_DEF_SIZE=399360, the map is no longer surrounded by blank space, but the screen loads slowly and there is screen tearing. Do you have any other suggestions?

[mverch67]

LV_CACHE_DEF_SIZE (in bytes) cannot be bigger than the RAM_SIZE (in kB). I suggest to set it to 6x 192kB to cache 6 map tiles.

What values does the memory display at the home screen show after this setting?

[Quency-D]

The image below is a screenshot taken after configuring 6x 192kB. The map is still the same as in the initial video.

-D LV_CACHE_DEF_SIZE=1179648

[mverch67]

The issue is that decoded png tiles use a huge amount of RAM because of a BUG/limitation in lvgl:
https://github.com/lvgl/lvgl/blob/7b549cf3bef9880da5b8e073cc594f54bfb6b54b/src/libs/lodepng/lv_lodepng.c#L247

If it would use RGB565 format instead of ARGB8888 all the map tiles would fit into the cache.

Note, that the V4 is the first device that has only 2MB PSRAM (instead of 4 or 8MB for other esp32 devices).

[Quency-D]

This is indeed a problem. Do you have any good ideas to improve it?

[mverch67]

See #295.

Heltec V4 requires the following settings in platformio.ini when not using SD card:

  -D MAP_TILES_GREY ; required for 2MB PSRAM
  -D RAM_SIZE=1432
  -D STBI_ARENA_SIZE=450000
  -D LV_CACHE_DEF_SIZE=0

[Quency-D]

This is absolutely fantastic.