ESP32-WROVER DevKit Display Issues: How to?

sittingduck
Posts: 5
Joined: Thu Mar 28, 2019 9:35 am

ESP32-WROVER DevKit Display Issues: How to?

Postby sittingduck » Sat Jun 22, 2019 8:42 am

So I got myself a ESP32-WROVER DevKit with the Display on the back. According to some documents, this is an ILI9341 display.

The only thing I really could get to work with the display was the stock demo: https://github.com/espressif/esp-idf/tr ... spi_master
But this demo does not contain any libraries for easy writing of text etc. I do not want to build a low level library myself just to display some sensor values. You need to know, that I do NOT want to program with Arduino, I would like to use the plain esp-idf framework.

Thus, I googled and found this one: https://github.com/MartyMacGyver/ESP32_Adafruit_ILI9341
This appears to be want I am looking for according to the linked demo (https://www.youtube.com/watch?v=VraLl8X ... e=youtu.be).

The project compiles fine with the current esp toolchain (v2019):

Code: Select all

$ make clean && make -j4 all && make flash monitor
But the display stays black and I get the following output from the monitor:

Code: Select all

rst:0x1 (POWERON_RESET),boot:0x1e (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0018,len:4
load:0x3fff001c,len:6660
load:0x40078000,len:11624
load:0x40080400,len:6684
entry 0x4008076c
I (28) boot: ESP-IDF v4.0-dev-837-g58df1d93b 2nd stage bootloader
I (28) boot: compile time 10:21:51
I (28) boot: Enabling RNG early entropy source...
I (34) boot: SPI Speed      : 40MHz
I (38) boot: SPI Mode       : DIO
I (42) boot: SPI Flash Size : 4MB
I (46) boot: Partition Table:
I (50) boot: ## Label            Usage          Type ST Offset   Length
I (57) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (65) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (72) boot:  2 factory          factory app      00 00 00010000 00100000
I (80) boot: End of partition table
I (84) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x0b200 ( 45568) map
I (109) esp_image: segment 1: paddr=0x0001b228 vaddr=0x3ffb0000 size=0x01de8 (  7656) load
I (112) esp_image: segment 2: paddr=0x0001d018 vaddr=0x40080000 size=0x00400 (  1024) load
0x40080000: _WindowOverflow4 at /Users/.../esp32/esp-idf/components/freertos/xtensa_vectors.S:1778

I (116) esp_image: segment 3: paddr=0x0001d420 vaddr=0x40080400 size=0x02bf0 ( 11248) load
I (129) esp_image: segment 4: paddr=0x00020018 vaddr=0x400d0018 size=0x182c4 ( 99012) map
0x400d0018: _stext at ??:?

I (169) esp_image: segment 5: paddr=0x000382e4 vaddr=0x40082ff0 size=0x052b0 ( 21168) load
0x40082ff0: timer_alarm_isr at /Users/.../esp32/esp-idf/components/esp32/esp_timer_esp32.c:274

I (183) boot: Loaded app from partition at offset 0x10000
I (183) boot: Disabling RNG early entropy source...
I (184) cpu_start: Pro cpu up.
I (187) cpu_start: Application information:
I (192) cpu_start: Project name:     testje
I (197) cpu_start: App version:      v1.01-11-gc3feb27-dirty
I (203) cpu_start: Compile time:     Jun 22 2019 10:21:54
I (209) cpu_start: ELF file SHA256:  b2b7fb0f4d566b56...
I (215) cpu_start: ESP-IDF:          v4.0-dev-837-g58df1d93b
I (222) cpu_start: Starting app cpu, entry point is 0x40080e84
0x40080e84: call_start_cpu1 at /Users/.../esp32/esp-idf/components/esp32/cpu_start.c:265

I (0) cpu_start: App cpu up.
I (232) heap_init: Initializing. RAM available for dynamic allocation:
I (239) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (245) heap_init: At 3FFB2E40 len 0002D1C0 (180 KiB): DRAM
I (251) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (258) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (264) heap_init: At 400882A0 len 00017D60 (95 KiB): IRAM
I (270) cpu_start: Pro cpu start user code
I (288) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
E (10289) task_wdt: Task watchdog got triggered. The following tasks did not reset the watchdog in time:
E (10289) task_wdt:  - IDLE0 (CPU 0)
E (10289) task_wdt: Tasks currently running:
E (10289) task_wdt: CPU 0: main
E (10289) task_wdt: CPU 1: IDLE1
Who can help me her? Why the watchdog is triggered?

Who is online

Users browsing this forum: No registered users and 284 guests