Toolchain xtensa-esp32-elf-win32-esp32-2019r1-8.2.0.zip missing

[rudi ;-)]

+

ok, it looks like for the esp32s2beta automatically generated projectname/build/esp32s2beta/component_project_vars.mk
there is no context just in time

Code: Select all

# COMPONENT_CONFIG_ONLY target sets no variables here

for compare, esp32 automatically generated projectname/build/esp32/component_project_vars.mk looks like

Code: Select all

# Automatically generated build file. Do not edit.
COMPONENT_INCLUDES += $(IDF_PATH)/components/esp32/include
COMPONENT_LDFLAGS += -L$(BUILD_DIR_BASE)/esp32 -lesp32 -L $(IDF_PATH)/components/esp32/ld -T esp32_out.ld -u ld_include_panic_highint_hdl -T $(BUILD_DIR_BASE)/esp32/esp32.project.ld -T esp32.peripherals.ld 
COMPONENT_LINKER_DEPS += $(IDF_PATH)/components/esp32/ld/esp32.peripherals.ld $(BUILD_DIR_BASE)/esp32/esp32.project.ld
COMPONENT_SUBMODULES += 
COMPONENT_LIBRARIES += esp32
COMPONENT_LDFRAGMENTS += $(IDF_PATH)/components/esp32/ld/esp32_fragments.lf $(IDF_PATH)/components/esp32/linker.lf
component-esp32-build: 

so my question:

is GNU Make just in time supported for ESP32s2Beta or we need CMAKE+Ninja...
i use not idf.py and i use not cmake in this handmake -
i want use esp32s2beta toolchain with GNU Make with ESP-IDF 4.0 ...

i will try further things..
- search in specificy (ESP32) makefiles for add's for add inlcudes in specificy (esp32s2beta) component_project_vars.mk automatically
- other further things

best wishes
rudi

[rudi ;-)]

+

project/build/esp32s2beta/component_project_vars.mk
(handmade)

Code: Select all

# COMPONENT_CONFIG_ONLY target sets no variables here
COMPONENT_INCLUDES += $(IDF_PATH)/components/esp32s2beta/include
COMPONENT_LDFLAGS += -L$(BUILD_DIR_BASE)/esp32s2beta -lesp32s2beta -L $(IDF_PATH)/components/esp32s2beta/ld -T esp32s2beta_out.ld -u ld_include_panic_highint_hdl -T $(BUILD_DIR_BASE)/esp32s2beta/esp32s2beta.project.ld -T esp32s2beta.peripherals.ld 
COMPONENT_LINKER_DEPS += $(IDF_PATH)/components/esp32s2beta/ld/esp32s2beta.peripherals.ld $(BUILD_DIR_BASE)/esp32s2beta/esp32s2beta.project.ld
COMPONENT_SUBMODULES += 
COMPONENT_LIBRARIES += esp32s2beta
COMPONENT_LDFRAGMENTS += $(IDF_PATH)/components/esp32s2beta/ld/esp32s2beta_fragments.lf $(IDF_PATH)/components/esp32s2beta/linker.lf
component-esp32s2beta-build: 

helps to find the esp32s2beta/soc includes ..

now small error.

Code: Select all

..
C:/msys32/home/sysop/esp32s2/esp-idf/components/soc/esp32s2beta/include/soc/cpu.h: In function 'cpu_init_memctl':
C:/msys32/home/sysop/esp32s2/esp-idf/components/soc/esp32s2beta/include/soc/cpu.h:57:2: error: #error "Shouldn't have this errata or need this call on esp32s2beta"
 #error "Shouldn't have this errata or need this call on esp32s2beta"
  ^~~~~
CC build/coap/libcoap/src/address.o
..

try further things..

- search the error level message and check it out

Code: Select all

static inline void cpu_init_memctl()
{
#if XCHAL_ERRATUM_572
#error "Shouldn't have this errata or need this call on esp32s2beta"
#endif
}

best wishes
rudi

[rudi ;-)]

+
ok - i run outside now

Code: Select all

CC build/bootloader/efuse/src/esp_efuse_fields.o
C:/msys32/home/sysop/esp32s2/esp-idf/components/efuse/src/esp_efuse_fields.c:17:10: fatal error: esp_efuse_table.h: No such file or directory
 #include "esp_efuse_table.h"
          ^~~~~~~~~~~~~~~~~~~
compilation terminated.

a look in the efuse components, there is only esp32 folder, a handmake copy the folder esp32 to esp32s2beta helps dirty,
but in next moment there are next things missed or not defined. **)

i see, there is an esp32s2beta target, what used parts of esp32 folders and othersides there are named esp32s2beta folders
if we setup basicly the target to esp32s2beta in next moment the compiler search in esp32s2beta folders,
but need just only shared esp32 things, and there is no esp32s2beta context in it.

**)
It takes longer to analyze when the target esp32s2beta is happy with shared esp32 stuff or needs an extra folder and settings.
i know, it is done with the installer and cmake and using idf.py
but hey - we are using GNU make
i did want try GNU Make and the ESP32S2Beta toolchain for simply hello world compile.
there are some things for it to do by hand.
perhabs i will search further, but just in time, there is no need for me honest,
cause i have no Chip7, MARLIN3 ,ESP32S2 or ESP32Sx,
am on the "blacklist" i think
no problem


best wishes
rudi

[rudi ;-)]

+

Code: Select all

...
Project build complete. To flash, run this command:
../../esp-idf/components/esptool_py/esptool/esptool.py -p (PORT) -b 460800 --after hard_reset write_flash --flash_mode
 dio --flash_size detect --flash_freq 40m 0x1000 build/bootloader/bootloader.bin 0x8000 build/partition_table/partitio
n-table.bin 0x10000 build/hello-world.bin
or run 'idf.py -p (PORT) flash'
...

460800?
ok.

now we wait for the available hardware.


best wishes
rudi

[rudi ;-)]

this was a nice drift away from the posted theme

hi guys
back to my cause for the post:

ESP32S2 Basics: How To use ESP-IDF on ESP32-S2 Beta chip
there is described, that we can download the esp32s2 toolchain for windows at
"dl.espressif.com/dl/toolchains/preview/xtensa-esp32s2-elf-gcc8_2_0-esp32s2-dev-4-g3a626e-win32.zip"

the future/esp32s2beta repo need toolchain version
esp32-2019r1

the on top linked toolchain but is
esp32s2-dev-4-g3a626e93

where we get the matched toolchain to the future/esp32s2beta IDF version?



btw:
few people set the environment path not case sensitive,
example export IDF_PATH = "c:/home/esp32s2/esp-idf"
it is then c:/home/esp32s2/esp-idf
but the file folder name comes back with C:/home/esp32s2/esp-idf
the STREQUAL in the cmake file will allways fail and gives warning,

Code: Select all

if(idf_path)
        if(NOT idf_path STREQUAL _idf_path)
            message(WARNING "IDF_PATH environment variable is different from inferred IDF_PATH.
                            Check if your project's top-level CMakeLists.txt includes the right
                            CMake files. Environment IDF_PATH will be used for the build.")
        endif()

suggestion: create extra VARs with TOLOWER
example:

Code: Select all

..
set(idf_path $ENV{IDF_PATH})
string(TOLOWER "${idf_path}" idf_path_lower)
..

thank you for your help

best wishes
rudi

[ESP_Angus]

Hi rudi,

the future/esp32s2beta repo need toolchain version
esp32-2019r1

the on top linked toolchain but is
esp32s2-dev-4-g3a626e93

where we get the matched toolchain to the future/esp32s2beta IDF version?

The esp32-2019r1 toolchain is for ESP32 only. For ESP32-S2 you have the correct toolchain.

Note that GNU Make build system does not support ESP32-S2, so anything you find in a .mk file may not be correct for ESP32-S2.

few people set the environment path not case sensitive,
example export IDF_PATH = "c:/home/esp32s2/esp-idf"
it is then c:/home/esp32s2/esp-idf
but the file folder name comes back with C:/home/esp32s2/esp-idf
the STREQUAL in the cmake file will allways fail and gives warning,

Thank you, will fix this for users with case insensitive filesystems.

Angus