Problem with lvgl

ESPHome
1

Hi I have started a small lvgl project using esp32-wrover (8MB PSRAM) and il9488 and xpt2046. But when I run the program, the screen turns black and does not respond.
The project without lvgl has no problems and the display and xpt2046 work properly.


spi:
  clk_pin: 41  ##display SCK and T_CLK
  mosi_pin: 42 ##display SDI(MOSI)/touch T_DIN
  miso_pin: 40 ##display SDO(MISO)/touch T_DO    


display:
  - platform: ili9xxx
    model: ILI9488_A
    cs_pin: 1
    dc_pin: 2
    reset_pin: 5
    invert_colors: false
    auto_clear_enabled: false
    update_interval: never
    id: my_display

touchscreen:
  platform: xpt2046
  id: touch
  cs_pin: 7
  interrupt_pin: 15
  update_interval: 50ms
  threshold: 400
  calibration:
    x_min: 289
    x_max: 3752
    y_min: 211
    y_max: 3868
  transform:
    mirror_x: true
    mirror_y: true
    swap_xy: true
  on_touch:
    - lambda: |-
          ESP_LOGI("cal", "x=%d, y=%d, x_raw=%d, y_raw=%0d",
              touch.x,
              touch.y,
              touch.x_raw,
              touch.y_raw
              );
lvgl:
  displays:
    - my_display
  pages:
    - id: main_page
      widgets:
        - label:
            align: CENTER
            text: 'Hello World!'

Please help

1000163523
10001635231920Ă—2560 373 KB

2

Any errors in the logs? Can we see the rest of your code?

Can you make sure the text is white?

text_color: 0x000000
1 Like
3

I tested the text with different colors. And there is no error in the log

esphome:
  name: 15-biglcd-lvgl
  on_boot:
    then:
      

esp32:
  board: esp32-s3-devkitc-1
  framework:
    type: arduino

# Enable logging
logger:
    logs:
     component: none
     sensor: none
     http_request: none
     text_sensor: none

# Enable Home Assistant API
api:
 reboot_timeout: 0s
  
ota:
- platform: esphome
  password: !secret ota_password
 

wifi:
   ssid: !secret wifi_ssid
   password: !secret wifi_password
   reboot_timeout: 0s
  #  manual_ip:
  #    static_ip: 192.168.1.115
  #    gateway: 192.168.1.1
  #    subnet: 255.255.255.0
  #    dns1: 8.8.8.8
  #    dns2: 4.4.4.4
  # Enable fallback hotspot (captive portal) in case wifi connection fails
   ap:
    ssid: "15-biglcd-lvgl"
    password: !secret web_server_password

web_server:
  port: 80
  auth:
    username: admin
    password: !secret web_server_password

psram:
    mode: octal
    speed: 80MHz

binary_sensor:
  - platform: status
    name: "Node Status"
    id: system_status


debug:
  update_interval: 15s

text_sensor:
  - platform: debug
    device:
      name: "Device Info"
    reset_reason:
      name: "Reset Reason"

sensor:
  - platform: debug
    free:
      name: "Heap Free"
    block:
      name: "Heap Max Block"
    loop_time:
      name: "Loop Time"
    psram:
      name: "Free PSRAM"

spi:
  clk_pin: 41  ##display SCK and T_CLK
  mosi_pin: 42 ##display SDI(MOSI)/touch T_DIN
  miso_pin: 40 ##display SDO(MISO)/touch T_DO    


display:
  - platform: ili9xxx
    model: ILI9488_A
    cs_pin: 1
    dc_pin: 2
    reset_pin: 5
    invert_colors: false
    auto_clear_enabled: false
    update_interval: never
    id: my_display

touchscreen:
  platform: xpt2046
  id: touch
  cs_pin: 7
  interrupt_pin: 15
  update_interval: 50ms
  threshold: 400
  calibration:
    x_min: 289
    x_max: 3752
    y_min: 211
    y_max: 3868
  transform:
    mirror_x: true
    mirror_y: true
    swap_xy: true
  on_touch:
    - lambda: |-
          ESP_LOGI("cal", "x=%d, y=%d, x_raw=%d, y_raw=%0d",
              touch.x,
              touch.y,
              touch.x_raw,
              touch.y_raw
              );
lvgl:
  displays:
    - my_display
  pages:
    - id: main_page
      widgets:
        - label:
            align: CENTER
            text: 'Hello World!'
4

Do you need to add your touchscreen id to lvgl?

You have this.

Should it be like this?

I cant really see that being the cause for your black screen but, it didnt look right.

1 Like
5

Hello, using touch had no effect on the blank screen

6

Make sure you are updated to 2024.8.1 there are LVGL bug fixes in this release

Are you turning on the backlight for the screen?

Rename your touchscreen to my_touchscreen then use the code below. my_touchscreen is the name in a lot of examples and it’s good to keep consistency. The new format is to use - display_id: name instead of just - name

lvgl:
  displays:
    - display_id: my_display
  touchscreens:
    - touchscreen_id: my_touchscreen
1 Like
7

Ya, i didnt think it was the primary issue, just thought id throw the suggestion out there to try.

If I were you, id go ask in the Esphome Discord channel. Thats where all the developers and really smart people hang out. Youll shouldnt have a problem getting help in there.

1 Like
8

Hi, I am using the latest version 2024.8.3
And there is no problem with my backlight and I display any text and image on the LCD with lambda

I even tested with a st7789v LCD and a new esp32-s3 board and had exactly the same problem.

I changed the name of the touch screen to my_touchscreen, but the problem is still not solved

9

Thanks for your suggestion
Can you give me the address of the discord channel?

10

Today I tested with ssd1306 and esp32 and I had the same problem

1000164777
10001647771920Ă—2560 259 KB

Does anyone really know where the problem comes from??

11

First confirm your display is working - remove the LVGL stuff and add show_test_card: true and remove update_interval: never in the display config. That should show a test pattern.

Then restore the LVGL config, get rid of the “none” settings for logs (component at least) and copy the complete serial log and post it here.

Are you sure your chip has octal PSRAM? You should see lines like this in the log:

[20:52:10]I (287) MSPI Timing: PSRAM timing tuning index: 10
[20:52:10]I (288) esp_psram: Found 8MB PSRAM device
[20:52:10]I (288) esp_psram: Speed: 80MHz
[20:52:10]I (321) mmu_psram: Read only data copied and mapped to SPIRAM
[20:52:10]I (408) mmu_psram: Instructions copied and mapped to SPIRAM
[20:52:10]I (408) cpu_start: Multicore app

Then at some point you should see:

[21:02:11][C][lvgl:284]: LVGL Setup starts
[21:02:11][C][lvgl:335]: LVGL Setup complete

When the log does the config dump (magenta color) there should be a line like this:

[20:52:15][C][lvgl:086]: LVGL:

You should not see:

[20:58:31][E][component:082]:   Component lvgl is marked FAILED

But with your current config you won’t anyway, since you are filtering out all component logs.

You could try setting buffer_size: 25% in the LVGL config - that should enable it to work even without PSRAM.

Posting the complete log here will help diagnosis.

2 Likes
12

Hello, I tested with this method and there was no problem with the LCD

[20:02:12][C][psram:020]: PSRAM:
[20:02:12][C][psram:021]:   Available: NO
[20:02:12][C][status:034]: Status Binary Sensor 'Node Status'
[20:02:12][C][status:034]:   Device Class: 'connectivity'
[20:02:12][C][lvgl:032]: LVGL:
[20:02:12][E][component:082]:   Component lvgl is marked FAILED

The model I have is ESP32-S3-DevKitC-1 , M0N16R8, but I don’t know what is the cause of this error.

1000165164
10001651641080Ă—2400 302 KB

13

My problem was solved by adding these few lines,
thanks to everyone who helped me

esphome:
  name: "15-disp-lvgl"
  platformio_options:
      build_flags: "-DBOARD_HAS_PSRAM"
      board_build.arduino.memory_type: qio_opi

[11:04:42][C][psram:020]: PSRAM:
[11:04:42][C][psram:021]:   Available: YES
[11:04:42][C][psram:024]:   Size: 8191 KB

1000165203
10001652031920Ă—2560 245 KB

1 Like
14

buffer_size: 25% was the magic for me.
I’m using a ESP32-VROOM.

15

I am also struggling to get LVGL working on a 7.3inch 5 colour + BW E Paper screen on an ESP32 wrover b board (allegedly contains PSRAM).

spi:
  clk_pin: 18
  mosi_pin: 23

display:
  - platform: waveshare_epaper
    id: epaper
    cs_pin:
      number: 5
      ignore_strapping_warning: True
    dc_pin: 27
    busy_pin:
      number: 25
      inverted: true
    reset_pin: 26
    model: 7.30in-f
     . . .

Neither of the fixes mentioned above appear to work.

Adding buffer_size had no effect:

lvgl:
  buffer_size: 25% 
  . . .

Component lvgl is marked FAILED

While this addition fails to compile:

esphome:
   platformio_options:
     build_flags: "-DBOARD_HAS_PSRAM"
     board_build.arduino.memory_type: qio_opi

saying:

In file included from /data/cache/platformio/packages/toolchain-xtensa-esp32/xtensa-esp32-elf/sys-include/sys/reent.h:503,
                 from /data/cache/platformio/packages/framework-arduinoespressif32/tools/sdk/esp32/include/newlib/platform_include/sys/reent.h:17,
                 from /data/cache/platformio/packages/toolchain-xtensa-esp32/xtensa-esp32-elf/sys-include/stdio.h:60,
                 from /data/cache/platformio/packages/framework-arduinoespressif32/cores/esp32/Arduino.h:27,
                 from src/esphome/core/macros.h:7,
                 from src/esphome/core/defines.h:2,
                 from src/esphome/components/api/api_connection.h:3,
                 from src/esphome/components/api/api_connection.cpp:1:
/data/cache/platformio/packages/framework-arduinoespressif32/tools/sdk/esp32/include/newlib/platform_include/assert.h:20:10: fatal error: sdkconfig.h: No such file or directory

I have tried building this on MacOS with esphome installed, plus on a HAYellow.

Any ideas how to resolve the build issue?

16

I’d suggest adding psram: to your config, switching to esp-idf and removing the platormio_options to start with.

1 Like
17

WOW!!
It took a few goes, acted broken for a while but ultimately worked!!
:clap:

1 Like
18

I am trying another project using a big e-paper screen with LVGL and am having problems again.
Tried the fixes that worked before.

The first confusing issue is with PSRAM.
I purchased an ESP32S2 which is supposed to have 2Meg of PSRAM. During startup, I see the following lines:

[14:18:42][C][psram:016]: PSRAM:
[14:18:42][C][psram:019]:   Available: NO

I have psram: in my config as suggested.

My display is a WaveShare 7.5” B+W, it came with HAT Rev 2.3. I am trying to use the driver 7.50inV2p . I have tried other ones.
NB. The HAT has a new pin (currently unused) called PWR - unsure of it’s purpose.

The project with LVGL always reports that LVGL failed to setup.
I followed the advice above and commented out the LVGL, then made the adjustments to display the test card. All that is drawn is a thin border with a little square in one corner.

This is the unique part of the test config:

esp32:
  board: lolin_s2_mini
  variant: ESP32S2
  framework:
    type: esp-idf

psram:

spi:
  clk_pin: 36
  mosi_pin: 35

display:
  - platform: waveshare_epaper
    id: epaper
    cs_pin: 34
    dc_pin: 17
    busy_pin:
      number: 16
      inverted: true
    reset_pin: 18
    model: 7.50inV2p
    show_test_card: true

I am lost :man_shrugging:

19

There is something weird happening here.

Trying a new Xiao ESP32 S3 (previously trying a Wemos S2 Mini), so this time I should have far more PSRAM for running LVGL apps :crossed_fingers:

during the USB provisioning I see the following messages:

Connected to ESP32-S3 on /dev/cu.usbmodem1101:
Chip type:          ESP32-S3 (QFN56) (revision v0.2)
Features:           Wi-Fi, BT 5 (LE), Dual Core + LP Core, 240MHz, Embedded PSRAM 8MB (AP_3v3)
Crystal frequency:  40MHz
…

Then during boot I see:

[16:42:12][C][psram:016]: PSRAM:
[16:42:12][C][psram:019]:   Available: NO

I have the following relevant lines in my config:

esp32:
  board: seeed_xiao_esp32s3
  variant: ESP32S3
  framework:
    type: esp-idf

psram:

Two chips in a row, I am doing something wrong or am spectacularly unlucky with my purchases … I suspect the former …

Any ideas?

20

Have you considered trying an all in one screen+CPU? No wiring and works out of the box!!