You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a bug in the ESP-IDF itself but as suggested by @suda-morrisin this post on the esp-idf repo side the workaround can't be tested since IDF is pre-compiled as a lib in the arduino framework.
Would it be possible to have a test branch where tesp-idf is pre-compiled with the workaround definition --> #define LCD_DMA_DESCRIPTOR_BUFFER_MAX_SIZE 4032
Sketch
The official RGB example on a board with flash encryption enabled.
Debug Message
E (1417) lcd_panel.rgb: lcd_rgb_panel_init_trans_link(1072): mount DMA frame buffer failed
E (1420) lcd_panel.rgb: esp_lcd_new_rgb_panel(355): init DMA link failed
ESP_ERROR_CHECK failed: esp_err_t 0x102 (ESP_ERR_INVALID_ARG) at 0x4202fead
#0 0x4202fead in EspNativeDisplayController::initializeLCD(_lv_disp_drv_t*) at frontend-controls/embedded-ui/driver/esp_drv.h:157 (discriminator 2)
file: "frontend-controls/embedded-ui/driver/esp_drv.h" line 157
func: esp_err_t EspNativeDisplayController::initializeLCD(lv_disp_drv_t*)
expression: esp_lcd_new_rgb_panel(&panel_config, &panel_handle)
abort() was called at PC 0x40382fdf on core 1
Backtrace: 0x40377316:0x3fcce310 0x40382fe9:0x3fcce330 0x40389ccd:0x3fcce350 0x40382fdf:0x3fcce3d0 0x4202fead:0x3fcce400 0x4202ffb7:0x3fcce4e0 0x42030087:0x3fcce500 0x42030d34:0x3fcce530 0x42099ec3:0x3fcce550 0x403840e6:0x3fcce570
#0 0x40377316 in panic_abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_system/panic.c:463
#1 0x40382fe9 in esp_system_abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_system/port/esp_system_chip.c:92
#2 0x40389ccd in abort at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/newlib/abort.c:38
#3 0x40382fdf in _esp_error_check_failed at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/esp_system/esp_err.c:49
#4 0x4202fead in EspNativeDisplayController::initializeLCD(_lv_disp_drv_t*) at frontend-controls/embedded-ui/driver/esp_drv.h:157 (discriminator 2)
#5 0x4202ffb7 in lcd_init() at frontend-controls/embedded-ui/ui.cpp:149
#6 0x42030087 in lvglPinnedCoreTask() at frontend-controls/embedded-ui/ui.cpp:309
#7 0x42030d34 in setup() at frontend-controls/main.cpp:202
#8 0x42099ec3 in loopTask(void*) at ./platformio/packages/framework-arduinoespressif32/cores/esp32/main.cpp:59
#9 0x403840e6 in vPortTaskWrapper at /home/runner/work/esp32-arduino-lib-builder/esp32-arduino-lib-builder/esp-idf/components/freertos/FreeRTOS-Kernel/portable/xtensa/port.c:139
ELF file SHA256: 0c7f495ca
E (1676) esp_core_dump_flash: Core dump flash config is corrupted! CRC=0x7bd5c66f instead of 0x0
E (1684) esp_core_dump_elf: Elf write init failed!
E (1688) esp_core_dump_common: Core dump write failed with error=-1
Rebooting...
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
I confirm I have checked existing issues, online documentation and Troubleshooting guide.
The text was updated successfully, but these errors were encountered:
Board
ESP32S3
Device Description
Esp32s3 based lcd.
Hardware Configuration
ESP32 in RGB config.
Version
latest master (checkout manually)
IDE Name
VSCode
Operating System
Windows 11
Flash frequency
80MHz
PSRAM enabled
yes
Upload speed
921600
Description
This is a bug in the ESP-IDF itself but as suggested by @suda-morris in this post on the esp-idf repo side the workaround can't be tested since IDF is pre-compiled as a lib in the arduino framework.
Would it be possible to have a test branch where tesp-idf is pre-compiled with the workaround definition -->
#define LCD_DMA_DESCRIPTOR_BUFFER_MAX_SIZE 4032
Sketch
Debug Message
Other Steps to Reproduce
No response
I have checked existing issues, online documentation and the Troubleshooting Guide
The text was updated successfully, but these errors were encountered: