Closed marcosp32 closed 2 years ago
Hi @marcosp32 ! ESP-IDF v4.4 is not supported yet and hence S3-based boards cannot be used with this framework.
Hi @valeros Any idea if it's supported already? I'm hitting this same error today 5 months afterwards.
@martinberlin Compiling for S3 works without any issues.
Can you please point me to a platformio.ini file where an ESP32 S3 board is setup along with esp-idf framework? Thanks a lot. I've lost a lot of time yesterday and could not make it work yet
@martinberlin This examples are working https://github.com/tasmota/platform-espressif32/tree/Tasmota/205x/examples/espidf-arduino-blink https://github.com/tasmota/platform-espressif32/tree/Tasmota/205x/examples/espidf-blink You may have to change the Gpio for the Led
CI Build https://github.com/Jason2866/platform-espressif32/actions/runs/3543518424
Ok great will try those. When I try like it's on the Platformio examples, get the same as @marcosp32
KeyError: 'toolchain-xtensa-esp32':
File "/home/martin/.platformio/penv/lib/python3.8/site-packages/platformio/builder/main.py", line 188:
env.SConscript("$BUILD_SCRIPT") ...
I would like to understand how to fix that too!
@martinberlin Which python version do you have installed? python --version
nvm just saw 3.8. Try this, delete the hidden folder .platformio
Platformio will rebuild. And do a pio upgrade. What version do you have platformio --version
EDIT: I use nowhere a python version < 3.9 Maybe?
Thanks Jason. Here it goes:
Deleted: rm -fr .platformio
Still opening it again:
PACKAGES:
- framework-espidf @ 3.40402.0 (4.4.2)
- tool-cmake @ 3.16.4
- tool-esptoolpy @ 1.40201.0 (4.2.1)
- tool-ninja @ 1.7.1
- toolchain-riscv32-esp @ 8.4.0+2021r2-patch3
- toolchain-xtensa-esp32s3 @ 8.4.0+2021r2-patch3
Reading CMake configuration...
KeyError: 'toolchain-xtensa-esp32':
File "/home/martin/.platformio/penv/lib/python3.8/site-packages/platformio/builder/main.py", line 188:
env.SConscript("$BUILD_SCRIPT")
Some more details
Distribution: Ubuntu 20.04.5 LTS
Thanks a lot for trying to help me. Other things like building esp32-arduino stuff goes fine. This happens only when trying to build espidf using esp32s3. If I build with any other environments it works correctly, so there has to be something with this board / MCU configuration. Just pushed the platformio.ini file: https://github.com/martinberlin/IT8951-esp32-epub-reader/blob/main/platformio.ini
Generating assembly for certificate bundle...
There was an issue with this Certificate Bundle thing? I'm kind of sure it's this! UPDATE: No it's not that there was something with the root certificate but it was in esp-idf 4.3
Ahh, you are the ePub guy :-) Now I know why this one looked somehow familiar to me Tbh, i am out of ideas at the moment. Try my fork, i changed a lot under the hood (using released IDF 4.4.3, toolchain patch5 and some others changes...)
[env:it8951_paper]
platform = https://github.com/tasmota/platform-espressif32/releases/download/v.2.0.5/platform-espressif32-v.2.0.5.zip
board = esp32-s3-devkitc-1
framework = espidf
; change microcontroller
board_build.mcu = esp32s3
;upload_port = /dev/cu.SLAB_USBtoUART
;monitor_port = /dev/cu.SLAB_USBtoUART
monitor_speed = 115200
monitor_filters = esp32_exception_decoder
board_build.partitions = partitions.csv
lib_deps =
https://github.com/leethomason/tinyxml2.git
build_flags =
; This is an M5 EPD display
-DBOARD_TYPE_M5_PAPER
; maximim speed
-Ofast
; needed to stop the png library tying to pull in Arduino.h
-D__MCUXPRESSO
; stop miniz conflicting with zlib which is used by the png library
-DMINIZ_NO_ZLIB_COMPATIBLE_NAMES
; device has PRSRAM
; and should be used for ram intensive display work
-DBOARD_HAS_PSRAM
; Setup display format and model via build flags - we're only using part of the epdiy codebase
; mainly the drawing code - but these settings will get us to compile and give us the correct
; display size
-DCONFIG_EPD_DISPLAY_TYPE_ED047TC2
-DCONFIG_EPD_BOARD_REVISION_LILYGO_T5_47
; setup the pins for the SDCard
-DSD_CARD_PIN_NUM_MISO=GPIO_NUM_13
-DSD_CARD_PIN_NUM_MOSI=GPIO_NUM_12
-DSD_CARD_PIN_NUM_CLK=GPIO_NUM_14
-DSD_CARD_PIN_NUM_CS=GPIO_NUM_4
; the adc channel that is connected to the battery voltage divider - this is GPIO_NUM_35
-DBATTERY_ADC_CHANNEL=ADC1_CHANNEL_7
; use SPIFFS - experimental feature
-D USE_SPIFFS
; Logging. Leave enabled for first builds and debugging. Comment to disable
-D LOG_ENABLED
lib_ignore =
touch
FT6X36
Have you transplanted the Lillygo ePaper display to an S3 ?
I will clone the repo (tomorrow) and try to compile the env variant which fails. EDIT: Offtopic. I have seen you did an LVGL implementation for ePaper. We implememted LVGL in Tasmota too but for the ePaper display our universal display driver is not ready...
I will try your take also. I’m using something similar to M5 but with a PCB that is sold by Goodisplay (called DEXA-C097) my own PCB is based on S3 and it’s just a very basic SPI master with RTC and 5V booster. Just for fun trying to make a 9.7 inch EPub reader. Thanks a lot for trying to help will try more also until I find what it is, is just that the error, does not give much hints
UPDATE: With platform = https://github.com/tasmota/platform-espressif32/releases/download/v.2.0.5/platform-espressif32-v.2.0.5.zip I can go further. Thanks a lot!
The board = esp32-s3-devkitc-1
does not have PSRAM.
S3 Flash / Psram with type QIO / OPI has to be 100% correct, if not device will not boot or bootloop. Whats the flash size and type and PSRAM size and type of your board?
With this let`s define a custom boards json. It is easy with platformio :-)
But this is not the reason for compile fail. Thats the next step of fun with the S3...
Thanks a lot @Jason2866 The Schematics of my S3 board are here With this I can already go forward. Created an Issue there in my fork so you can track my advance since I have the feeling we are communicating over here and it's starting to be Offtopic for the nice Platformio people.
Solution: The problem was a faulty Pio setup.
From: https://community.platformio.org/t/cant-build-for-esp32s3/28090
I am having issues compiling for a new esp module ESP32-WROOM-1U.
I can build just fine using idf.py build
I am using esp-idf.
This is the output:
Board file: