Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build with esp-idf-4.4.3 fails #327

Open
dannybackx opened this issue Dec 26, 2022 · 1 comment
Open

build with esp-idf-4.4.3 fails #327

dannybackx opened this issue Dec 26, 2022 · 1 comment
Labels
stale This will not be worked on

Comments

@dannybackx
Copy link

We use GitHub issues for development related discussions.
Please use the forum to ask questions.

Describe the issue
Followed the steps on https://github.com/lvgl/lv_port_esp32

Code to reproduce the issue

Expected Results

Actual Results

I (0) cpu_start: Starting scheduler on APP CPU.
I (40) lvgl_helpers: Display hor size: 480, ver size: 320
I (40) lvgl_helpers: Display buffer size: 19200
I (40) lvgl_helpers: Initializing shared SPI master
I (50) lvgl_helpers: Configuring SPI host HSPI_HOST (1)
I (60) lvgl_helpers: MISO pin: 19, MOSI pin: 23, SCLK pin: 18, IO2/WP pin: -1, IO3/HD pin: -1
I (60) lvgl_helpers: Max transfer size: 38400 (bytes)
I (70) lvgl_helpers: Initializing SPI bus...
I (80) disp_spi: Adding SPI device
I (80) disp_spi: Clock speed: 40000000Hz, mode: 0, CS pin: 17
E (80) spi_master: spi_master_init_driver(200): host_id not initialized

assert failed: tp_spi_add_device_config tp_spi.c:47 (ret==ESP_OK)

Backtrace: 0x40081a82:0x3ffc1270 0x400862d1:0x3ffc1290 0x4008bfa1:0x3ffc12b0 0x400f1915:0x3ffc13d0 0x400f194a:0x3ffc13f0 0x400f0f08:0x3ffc1440 0x400d5925:0x3ffc1470 0x40088fb1:0x3ffc1500
0x40081a82: panic_abort at /home/danny/src/github/esp32/esp-idf-v4.4.3/components/esp_system/panic.c:402

ESP32 Chip version

ESP-IDF version

Development kit used

Development machine OS

Compilation warnings/errors (if available)

If possible, copy the compilation log into a file and attach it here

@stale
Copy link

stale bot commented Apr 20, 2023

This issue or pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale This will not be worked on label Apr 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant