When setting up ESP32-S2 environment using command
idf.py set-target esp32-s2, an error occurred as “Error: No such command ‘set-target’”. What could be the reason?¶
The esp-idf is adapted to ESP32-S2 from release/v4.2, thus setting up ESP32-S2 environment in previous versions will cause errors. In this case, when using command
idf.py set-target esp32-s2, there will be error as “Error: No such command ‘set-target’”.
It is recommended to perform tests and development on ESP32-S2 using esp-idf release/v4.2 and later versions. For more information, please refer to ESP32-S2 Get Started.
When installing esp-idf version master using ESP-IDF Tools 2.3 in Windows system, an error occurred as: Installation has failed with exit code 2. What could be the reason?¶
This is related to the bad network environment. The github repository cannot be downloaded smoothly under such network environment, causing the SDK failed downloading on your PC.
When using esp-idf-tools-setup-2.2.exe in Windows system, a python error occurred during the installation:¶
Installation has failed with exit code 1
Update your tool chain: https://dl.espressif.com/dl/esp-idf-tools-setup-2.3.exe
Remove the obsolete option “–no-site-packages” from idf_tools.py
What should I do if I get
Download failed: security channel support error when installing build environment in Windows system?¶
This is due to the Windows system has disabled the SSl3.0 support by default.
Solution: Go to Control Panel and find
Internet option, select
Advancedand check the
use SSL 3.0option.
When executing export.bat in Windows system, what should I do if I get CMake, gdbgui version errors?¶
C:\Users\xxxx\.espressif\tools\cmake\3.16.4\bin The following Python requirements are not satisfied: gdbgui>=0.13.2.0
This is because the upstream gdbgui has been updated, thus it is not compatible with the low version of python. The current solution is to manually modify the root file
requirements.txtin esp-idf by changing the description of gdbgui version to
How to configure
IDF_PATH when developing ESP32 and ESP8266 simultaneously?¶
PATH, there is no need to do extra configurations. You can put them together as: export PATH=”$HOME/esp/xtensa-esp32-elf/bin:$HOME/esp/xtensa-lx106-elf/bin:$PATH”.
IDF_PATH, you can specify it for separate chips as:
In ESP32 related projects, use
IDF_PATH = $(HOME)/esp/esp-idf; in ESP8266 related projects, use
IDF_PATH = $(HOME)/esp/ESP8266_RTOS_SDK.