You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have compiled the hello_world example Get Started with ESP-IDF and the issue is not addressed there.
I have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
ESP-AT version
V3.4.0.0-125-g6b22e5aa
Operating System used
Windows
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
I expect to not corrupt the installation of ESP-IDF with Eclipse IDE, but after installing and running ESP-AT framework, the ESP-IDF with Eclipse IDE is not able to build the blink example, until a full reinstall of the framework.
What is the actual behavior?
Corrupts the installation of the ESP-IDF with Eclipse IDE
Steps to reproduce
Install ESP-IDF with Eclipse IDE. This installs framework V5.4.
Import blink example into the workspace
Build, download and test the example on ESP32-C3-Mini1
Close ESP-IDF/Eclipse IDE
Use command window to clone, install, configure, build and test ESP-AT (into its own separate directory)
Close command window
Reopen ESP-IDF/Eclipse IDE
Try to rebuild the blink project.
Now the blink project complains of wrong versions: "requirement 'esptool~=4.8' was not met. Installed version 4.7.0"
" requirement 'esp-idf-kconfig<3.0.0,>=2.0.2' was not met. Installed version 1.5.0
...
The only way I found to resolve that issue is to use ESP-IDF-Manager to remove the framework and reinstall it.
After reinstalling the framework, the blink project now builds and tests OK.
Now close ESP-IDF/Eclipse IDE
Open Command window (ESP-IDF5.4 CMD)
Switch to the directory for ESP-AT
Run "python build.py menuconfig"
The command ends with the following error: "ESP-IDF v5.1.5-196-g64849cb703-dirty A fatal error occured: idf.py build failed"
After that, reinstalling the ESP-AT project makes it build and work again, but then the blink project in the Eclipse IDE does not work again...
and so on...
Is it expected that both environments cannot cohabitate on the same computer?
Should I plan to use a dedicated computer to manage the ESP-AT project and another one to use with the ESP-IDF/Eclipse IDE environment?
Build or installation Logs
Log of menuconfig instantiation, after reinstalling ESP-IDF v5.4 framework in ESP/Eclipse-IDE:
---------------------------------------------------------------------------------------------------
C:\Espressif\frameworks\esp-idf-v5.4>cd C:\Users\Admin\Documents\MyDoc_Sup\Develop\ESP32_AT\esp-at
C:\Users\Admin\Documents\MyDoc_Sup\Develop\ESP32_AT\esp-at>python build.py menuconfig
Platform name:ESP32C3 Module name:MINI-1 Silence:0
submodules check completed for updates.
support_ext_partition.patch does not need to be applied.
patches check completed for updates.
Ready to set up environment variables..
PATH is C:\Espressif\frameworks\esp-idf-v5.4\components\espcoredump;C:\Espressif\frameworks\esp-idf-v5.4\components\partition_table;C:\Espressif\frameworks\esp-idf-v5.4\components\app_update;C:\Espressif\tools\xtensa-esp-elf-gdb\14.2_20240403\xtensa-esp-elf-gdb\bin;C:\Espressif\tools\riscv32-esp-elf-gdb\14.2_20240403\riscv32-esp-elf-gdb\bin;C:\Espressif\tools\xtensa-esp-elf\esp-14.2.0_20241119\xtensa-esp-elf\bin;C:\Espressif\tools\esp-clang\esp-18.1.2_20240912\esp-clang\bin;C:\Espressif\tools\riscv32-esp-elf\esp-14.2.0_20241119\riscv32-esp-elf\bin;C:\Espressif\tools\esp32ulp-elf\2.38_20240113\esp32ulp-elf\bin;C:\Espressif\tools\cmake\3.30.2\bin;C:\Espressif\tools\openocd-esp32\v0.12.0-esp32-20241016\openocd-esp32\bin;C:\Espressif\tools\ninja\1.12.1\;C:\Espressif\tools\idf-exe\1.0.3\;C:\Espressif\tools\ccache\4.10.2\ccache-4.10.2-windows-x86_64;C:\Espressif\tools\dfu-util\0.11\dfu-util-0.11-win64;C:\Espressif\tools\qemu-xtensa\esp_develop_9.0.0_20240606\qemu\bin;C:\Espressif\tools\qemu-riscv32\esp_develop_9.0.0_20240606\qemu\bin;C:\Espressif\frameworks\esp-idf-v5.4\tools;C:\Espressif\python_env\idf5.4_py3.11_env\Scripts\;C:\Espressif\tools\idf-git\2.44.0\cmd\;C:\Espressif;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\;C:\Program Files\IVI Foundation\VISA\Win64\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\Program Files\Git\cmd;C:\Users\Admin\AppData\Local\Programs\Python\Python312\Scripts\;C:\Users\Admin\AppData\Local\Programs\Python\Python312\;C:\Users\Admin\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\JetBrains\PyCharm Community Edition 2024.2.3\bin;
IDF_PYTHON_ENV_PATH is C:\Espressif\python_env\idf5.4_py3.11_env
sys.platform is win32
Not using an unsupported version of tool riscv32-esp-elf-gdb found in PATH: 14.2_20240403.
Not using an unsupported version of tool riscv32-esp-elf found in PATH: esp-14.2.0_20241119.
WARNING: The following issue occurred while accessing the ESP-IDF version file in the Python environment: [Errno 2] No such file or directory: 'C:\\Espressif\\python_env\\idf5.4_py3.11_env\\idf_version.txt'. (Diagnostic information. It can be ignored.)
export str is ESP_ROM_ELF_DIR=C:\Espressif\tools\esp-rom-elfs\20230320\
ESP_IDF_VERSION=5.1
PATH=C:\Espressif\tools\riscv32-esp-elf-gdb\12.1_20231023\riscv32-esp-elf-gdb\bin;C:\Espressif\tools\riscv32-esp-elf\esp-12.2.0_20230208\riscv32-esp-elf\bin;C:\Espressif\tools\cmake\3.30.2\bin;C:\Espressif\tools\openocd-esp32\v0.12.0-esp32-20241016\openocd-esp32\bin;C:\Espressif\tools\ninja\1.12.1\;C:\Espressif\tools\idf-exe\1.0.3\;C:\Espressif\tools\ccache\4.10.2\ccache-4.10.2-windows-x86_64;C:\Users\Admin\Documents\MyDoc_Sup\Develop\ESP32_AT\esp-at\esp-idf\tools;%PATH%
IDF_DEACTIVATE_FILE_PATH=C:\Users\Admin\AppData\Local\Temp\tmpj7_iyc8_idf_15484
PATH is C:\Espressif\tools\riscv32-esp-elf-gdb\12.1_20231023\riscv32-esp-elf-gdb\bin;C:\Espressif\tools\riscv32-esp-elf\esp-12.2.0_20230208\riscv32-esp-elf\bin;C:\Espressif\tools\cmake\3.30.2\bin;C:\Espressif\tools\openocd-esp32\v0.12.0-esp32-20241016\openocd-esp32\bin;C:\Espressif\tools\ninja\1.12.1\;C:\Espressif\tools\idf-exe\1.0.3\;C:\Espressif\tools\ccache\4.10.2\ccache-4.10.2-windows-x86_64;C:\Users\Admin\Documents\MyDoc_Sup\Develop\ESP32_AT\esp-at\esp-idf\tools;%PATH%;C:\Espressif\frameworks\esp-idf-v5.4\components\espcoredump;C:\Espressif\frameworks\esp-idf-v5.4\components\partition_table;C:\Espressif\frameworks\esp-idf-v5.4\components\app_update;C:\Espressif\tools\xtensa-esp-elf-gdb\14.2_20240403\xtensa-esp-elf-gdb\bin;C:\Espressif\tools\riscv32-esp-elf-gdb\14.2_20240403\riscv32-esp-elf-gdb\bin;C:\Espressif\tools\xtensa-esp-elf\esp-14.2.0_20241119\xtensa-esp-elf\bin;C:\Espressif\tools\esp-clang\esp-18.1.2_20240912\esp-clang\bin;C:\Espressif\tools\riscv32-esp-elf\esp-14.2.0_20241119\riscv32-esp-elf\bin;C:\Espressif\tools\esp32ulp-elf\2.38_20240113\esp32ulp-elf\bin;C:\Espressif\tools\cmake\3.30.2\bin;C:\Espressif\tools\openocd-esp32\v0.12.0-esp32-20241016\openocd-esp32\bin;C:\Espressif\tools\ninja\1.12.1\;C:\Espressif\tools\idf-exe\1.0.3\;C:\Espressif\tools\ccache\4.10.2\ccache-4.10.2-windows-x86_64;C:\Espressif\tools\dfu-util\0.11\dfu-util-0.11-win64;C:\Espressif\tools\qemu-xtensa\esp_develop_9.0.0_20240606\qemu\bin;C:\Espressif\tools\qemu-riscv32\esp_develop_9.0.0_20240606\qemu\bin;C:\Espressif\frameworks\esp-idf-v5.4\tools;C:\Espressif\python_env\idf5.4_py3.11_env\Scripts\;C:\Espressif\tools\idf-git\2.44.0\cmd\;C:\Espressif;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin\;C:\Program Files\IVI Foundation\VISA\Win64\Bin\;C:\Program Files (x86)\IVI Foundation\VISA\WinNT\Bin;C:\Program Files\Git\cmd;C:\Users\Admin\AppData\Local\Programs\Python\Python312\Scripts\;C:\Users\Admin\AppData\Local\Programs\Python\Python312\;C:\Users\Admin\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\JetBrains\PyCharm Community Edition 2024.2.3\bin;
IDF_PYTHON_ENV_PATH is C:\Espressif\python_env\idf5.4_py3.11_env
The following Python requirements are not satisfied:
Requirement 'pyparsing<3.1,>=3.0.3' was not met. Installed version: 3.2.1
Requirement 'esptool~=4.7.0' was not met. Installed version: 4.8.1
Requirement 'cryptography<40,>=2.1.4' was not met. Installed version: 43.0.3
Requirement 'pyelftools<=0.29' was not met. Installed version: 0.31
Requirement 'esp-idf-kconfig<2.0.0,>=1.4.2' was not met. Installed version: 2.4.1
To install the missing packages, please run "install.bat"
Diagnostic information:
IDF_PYTHON_ENV_PATH: C:\Espressif\python_env\idf5.4_py3.11_env
Python interpreter used: C:\Espressif\python_env\idf5.4_py3.11_env\Scripts\python.exe
Constraint file: C:\Espressif\espidf.constraints.v5.1.txt
Requirement files:
- C:\Users\Admin\Documents\MyDoc_Sup\Develop\ESP32_AT\esp-at\esp-idf\tools\requirements\requirements.core.txt
Python being checked: C:\Espressif\python_env\idf5.4_py3.11_env\Scripts\python.exe
ESP-IDF v5.1.5-196-g64849cb703-dirty
A fatal error occurred: idf.py build failed
More Information
No response
The text was updated successfully, but these errors were encountered:
Answers checklist
ESP-AT version
V3.4.0.0-125-g6b22e5aa
Operating System used
Windows
If you are using Windows, please specify command line type.
CMD
What is the expected behavior?
I expect to not corrupt the installation of ESP-IDF with Eclipse IDE, but after installing and running ESP-AT framework, the ESP-IDF with Eclipse IDE is not able to build the blink example, until a full reinstall of the framework.
What is the actual behavior?
Corrupts the installation of the ESP-IDF with Eclipse IDE
Steps to reproduce
Is it expected that both environments cannot cohabitate on the same computer?
Should I plan to use a dedicated computer to manage the ESP-AT project and another one to use with the ESP-IDF/Eclipse IDE environment?
Build or installation Logs
More Information
No response
The text was updated successfully, but these errors were encountered: