Sysprogs forums › Forums › VisualGDB › ESP-IDF V5
Tagged: Espressif ESP32 ESP-IDF V5
- This topic has 29 replies, 6 voices, and was last updated 2 years ago by support.
-
AuthorPosts
-
December 6, 2022 at 06:11 #33505gojimmypiParticipant
The toolchain offline installer for ESP-IDF v5 is now a release as well:
https://github.com/espressif/idf-installer/releases/tag/online-2.17
(That’s a valid URL, even though it ends up as 404 when clicking on it; try to open manually with cut and paste. Seems the link seen here is somehow missing the “online” word)
December 9, 2022 at 22:12 #33523supportKeymasterThanks, we have tested the new toolchain together with the ESP-IDF 5.0 and confirm that the basic projects work for the ESP32, ESP32C3, ESP32C3, ESP32S2, ESP32C3 and ESP32H2 devices. We have also retested semihosting (regular ESP32 device only) and adjusted our unit test integration to be compatible with the latest ESP-IDF.
You can download the updated toolchain installer here: https://gnutoolchains.com/esp32/
Please note that ESP-IDF 5.0 uses its own system to manage virtual Python environments, so you would need the following VisualGDB build to use it automatically: VisualGDB-5.6.109.4769.msi
We will run a few further tests and will release an official VisualGDB 5.6R9 with full ESP-IDF 5.0 support in the next few days.
- This reply was modified 2 years ago by support.
December 13, 2022 at 06:03 #33539johncParticipantWith the latest toolchain and the experimental VisualGDB build I am getting a warning:
WARNING: ULP assembler version 2.28.51 is not supported. Expected to see
version: 2.35_20220830.followed by an error:
esp32ulp-elf-as: unrecognized option `–mcpu=esp32′
December 13, 2022 at 07:14 #33540johncParticipantA quick follow-up: upgraded the ULP assembler manually from the esp-idf distro to 2.35 and all is well now. Apparently this part was overlooked when building the latest toolchain and should be easily fixed.
December 13, 2022 at 11:03 #33542supportKeymasterThanks, we have fixed it and released an updated toolchain (esp32-gcc11.2.0-r2.exe).
December 16, 2022 at 17:09 #33553gojimmypiParticipantThe latest v5 install was a rather bumpy. I ran the esp32-gcc11.2.0-r2.exe noted above.
My existing project with ESP 4.4.2 seemed to have “forgotten” which toolchain version to use. Only the new v5 was visible in Visual Studio. Fortunately that toolchain was not (initially) deleted, but upon re-launching and selecting the existing 4.4.2 I received a message about needing to install the v5 toolchain that I just downloaded and installed manually. The new toolchain did not appear as an option to download from within Visual Studio.
Letting the Visual Studio “resolve” finish, and unfortunately it *did* wipe all but
v4.4.1
inC:\SysGCC\esp32\esp-idf
. I have no idea why that one was left, which of course I rarely use. Erg, I wish I had backed up that directory. I had several toolchains there, including non-Espressif components installed that I would have really preferred not to have deleted.The re-install was not very intuitive and of course tool a very long time with large downloads and re-installs.
Attachments:
You must be logged in to view attached files.December 16, 2022 at 17:12 #33556gojimmypiParticipantI just notice after all of that in my prior message: upon installing the v4.4.2 toolchain, the v5 that I just installed ended up getting deleted.
So I guess there’s no option at this time to have v4.x and v5.x installed side-by-side?
I need an environment were I can test with several toolchain versions.
Thank you
December 18, 2022 at 16:56 #33563supportKeymasterHi,
You can install both toolchains side-by-side, as long as you use the “online” view in the VisualGDB Package Manager and manually specify a different directory (or just download and run the installer manually). The “update” view is intended for replacing the older toolchains, and will indeed overwrite it.
For convenience, you can always select to ignore a specific update, so VisualGDB won’t suggest it anymore.
Regarding the IDF versions, it sounds like you had experimented with manually installing extra ESP-IDF checkouts into your toolchain, and they got removed when VisualGDB uninstalled the old toolchain during the update process. This is to be expected, as mixing the parts from the old and new toolchain could result in very weird bugs.
In general, if you are playing around with multiple ESP32 toolchain and IDF checkouts, we urge you to keep good notes of the toolchain and IDF versions that work together and double-checking them when you clone the IDF releases manually. Accidentally combining unsupported versions often leads to strange errors.
December 18, 2022 at 19:11 #33564gojimmypiParticipantHi & thanks for your reply.
First: no. It was not an “experiment”, and no: I was not “playing around”. I didn’t have an option to upgrade my VisualGDB application extension and I didn’t have ESP-IDF 5.0 listed as an option to install. I simply followed what I thought were instructions, above to install the download exe: “released an updated toolchain (esp32-gcc11.2.0-r2.exe).”
Some warning, such as “are you sure you want to delete existing toolchains” might have been nice.
December 19, 2022 at 12:37 #33570angelParticipanttoolchain update not found
Attachments:
You must be logged in to view attached files.December 20, 2022 at 18:46 #33574PaulMartinsenParticipantHi,
I’m receiving the following error when trying to use the v5 toolchain with VisualGDB:
-- Building ESP-IDF components for target esp32
-- Checking Python dependencies...
ERROR: C:\Users\Paul\.espressif\python_env\idf5.0_py3.8_env\Scripts\python.exe doesn't exist! Please run the install script or "idf_tools.py install-python-env" in order to create it
-- Configuring incomplete, errors occurred!
See also "Software/EmbeddedProject3/EmbeddedProject3/build/VisualGDB/Debug/CMakeFiles/CMakeOutput.log".
CMake Error at C:/Programming/Languages/VisualGDBTools/ESP32/v5/esp-idf/v5.0/tools/cmake/build.cmake:342 (message):
Some Python dependencies must be installed. Check above message for
details.
Call Stack (most recent call first):
C:/Programming/Languages/VisualGDBTools/ESP32/v5/esp-idf/v5.0/tools/cmake/build.cmake:480 (__build_check_python)
C:/Programming/Languages/VisualGDBTools/ESP32/v5/esp-idf/v5.0/tools/cmake/project.cmake:440 (idf_build_process)
CMakeLists.txt:6 (project)
System.Exception: CMake exited with code 1
at e43.l(n b, Object a)
This error occurs immediately after creating a new ESP32 project using the v5 toolchain, which would make it a “configuration phase” problem.
I got to this by:
- installing the trial from https://sysprogs.com/getfile/1914/VisualGDB-5.6r8-trial.msi, which setup and downloaded the 4.4.1 version of the IDF tools. That worked fine.
- Then I installed the v5 tools using this link: https://sysprogs.com/getfile/1959/esp32-gcc11.2.0-r2.exe. Which is when I first received the error.
- Above, you said that https://visualgdb.com/download/?build=5.6.109.4769 was needed for v5, so I installed that but it didn’t resolve the problem.
- Running C:\Programming\Languages\VisualGDBTools\ESP32\v5\esp-idf\v5.0\install.bat (suggested in the error message) succeeds but doesn’t resolve the problem either.
I’m a bit lost at this point. Any suggestions?
December 20, 2022 at 19:13 #33575PaulMartinsenParticipantI suspect the problem is that
IDF_TOOLS_PATH
isn’t treated consistently. Whether by Espressif’s tools or VisualGBD I’m not sure. But I noticed that runninginstall.bat
created a python environment at the path set byIDF_TOOLS_PATH
, but that wasn’t where VisualGDB was looking for it during the configuration phase. Removing the Espressif toolset and running theinstall.bat
from VisualGDB toolchain location resolved the problem at the expense of expanding the user’s profile folder by nearly 3GB.December 21, 2022 at 09:07 #33578gojimmypiParticipantI’m revisiting this today. The ESP-IDF v5 is still not working properly for me. I installed v5 the Visual Studio and tried to load cmake & build. Saw this error:
Running CMake: C:\Users\gojimmypi\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G "Ninja" -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=c:/sysgcc/esp32/tools/ninja/1.10.2/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0
-- Building ESP-IDF components for target esp32
-- Checking Python dependencies...
Python requirements are satisfied.
Constraint file: C:\Users\gojimmypi\.espressif\espidf.constraints.v5.0.txt
Requirement files:
- C:\SysGCC\esp32\esp-idf\v5.0\tools\requirements\requirements.core.txt
Python being checked: C:\Users\gojimmypi\.espressif\python_env\idf5.0_py3.8_env\Scripts\python.exe
CMake Error at C:/SysGCC/esp32/esp-idf/v5.0/tools/cmake/build.cmake:519 (message):
C:\SysGCC\esp32\esp-idf\v5.0\python-env\Scripts\python.exe: Error while
finding module specification for 'idf_component_manager.prepare_components'
(ModuleNotFoundError: No module named 'idf_component_manager')
Call Stack (most recent call first):
C:/SysGCC/esp32/esp-idf/v5.0/tools/cmake/project.cmake:440 (idf_build_process)
CMakeLists.txt:12 (project)
So I tried from commandline in WSL:
0 $ . /mnt/c/SysGCC/esp32/esp-idf/v5.0/export.sh
Resetting IDF_PATH from '/mnt/c/SysGCC/esp32/esp-idf/v4.4.2' to '/mnt/c/SysGCC/esp32/esp-idf/v5.0'
Detecting the Python interpreter
Checking "python3" ...
Python 3.8.10
"python3" has been detected
Checking Python compatibility
Checking other ESP-IDF version.
WARNING: No IDF variables to remove from environment found. Deactivation of previous esp-idf version was not successful.
Adding ESP-IDF tools to PATH...
ERROR: tool xtensa-esp-elf-gdb has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
ERROR: tool riscv32-esp-elf-gdb has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
ERROR: tool xtensa-esp32-elf has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
An unsupported version of tool xtensa-esp32-elf was found in PATH: esp-2021r2-patch3-8.4.0.
ERROR: tool xtensa-esp32s2-elf has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
An unsupported version of tool xtensa-esp32s2-elf was found in PATH: esp-2021r2-patch3-8.4.0.
ERROR: tool xtensa-esp32s3-elf has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
An unsupported version of tool xtensa-esp32s3-elf was found in PATH: esp-2021r2-patch3-8.4.0.
ERROR: tool riscv32-esp-elf has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
An unsupported version of tool riscv32-esp-elf was found in PATH: esp-2021r2-patch3-8.4.0.
ERROR: tool esp32ulp-elf has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
An unsupported version of tool esp32ulp-elf was found in PATH: 2.28.51.
Using a supported version of tool cmake found in PATH: 3.16.3.
However the recommended version is 3.24.0.
ERROR: tool openocd-esp32 has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
An unsupported version of tool openocd-esp32 was found in PATH: v0.11.0-esp32-20220411.
ERROR: tool esp-rom-elfs has no installed versions. Please run '/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh' to install it.
So ok, I close that session and started a new WSL and tried to run
/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh
I saw this error:
0 $ /mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh
Detecting the Python interpreter
Checking "python3" ...
Python 3.8.10
"python3" has been detected
Checking Python compatibility
Installing ESP-IDF tools
Current system platform: linux-amd64
Selected targets are: esp32s2, esp32c3, esp32c2, esp32, esp32s3, esp32h2
Installing tools: xtensa-esp-elf-gdb, riscv32-esp-elf-gdb, xtensa-esp32-elf, xtensa-esp32s2-elf, xtensa-esp32s3-elf, riscv32-esp-elf, esp32ulp-elf, openocd-esp32, esp-rom-elfs
Skipping xtensa-esp-elf-gdb@11.2_20220823 (already installed)
Skipping riscv32-esp-elf-gdb@11.2_20220823 (already installed)
Skipping xtensa-esp32-elf@esp-2022r1-11.2.0 (already installed)
Skipping xtensa-esp32s2-elf@esp-2022r1-11.2.0 (already installed)
Skipping xtensa-esp32s3-elf@esp-2022r1-11.2.0 (already installed)
Skipping riscv32-esp-elf@esp-2022r1-11.2.0 (already installed)
Skipping esp32ulp-elf@2.35_20220830 (already installed)
Skipping openocd-esp32@v0.11.0-esp32-20221026 (already installed)
Skipping esp-rom-elfs@20220823 (already installed)
Installing Python environment and packages
Creating a new Python environment in /home/gojimmypi/.espressif/python_env/idf5.0_py3.8_env
The virtual environment was not created successfully because ensurepip is not
available. On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.
apt install python3.8-venv
You may need to use sudo with that command. After installing the python3-venv
package, recreate your virtual environment.
Failing command: ['/home/gojimmypi/.espressif/python_env/idf5.0_py3.8_env/bin/python3', '-Im', 'ensurepip', '--upgrade', '--default-pip']
Traceback (most recent call last):
File "/mnt/c/SysGCC/esp32/esp-idf/v5.0/tools/idf_tools.py", line 2610, in <module>
main(sys.argv[1:])
File "/mnt/c/SysGCC/esp32/esp-idf/v5.0/tools/idf_tools.py", line 2602, in main
action_func(args)
File "/mnt/c/SysGCC/esp32/esp-idf/v5.0/tools/idf_tools.py", line 2022, in action_install_python_env
subprocess.check_call([sys.executable, '-m', 'venv',
File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/python3', '-m', 'venv', '--clear', '/home/gojimmypi/.espressif/python_env/idf5.0_py3.8_env']' returned non-zero exit status 1.
so ok, I ran
apt install python3.8-venv
0 $ sudo apt-get install python3.8-venv
[sudo] password for gojimmypi:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
gstreamer1.0-plugins-base libc-ares2 libcdparanoia0 libgstreamer-plugins-base1.0-0 liblua5.2-0 libopus0 liborc-0.4-0
libqt5multimedia5 libqt5multimedia5-plugins libqt5multimediagsttools5 libqt5multimediawidgets5 libsbc1 libsmi2ldbl libsnappy1v5
libspandsp2 libspeexdsp1 libssh-gcrypt-4 libtheora0 libvisual-0.4-0 libwireshark-data libwireshark13 libwiretap10 libwsutil11
wireshark-common wireshark-qt
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
libpython3.8 libpython3.8-dev libpython3.8-minimal libpython3.8-stdlib python3.8 python3.8-dev python3.8-minimal
Suggested packages:
python3.8-doc
The following NEW packages will be installed:
python3.8-venv
The following packages will be upgraded:
libpython3.8 libpython3.8-dev libpython3.8-minimal libpython3.8-stdlib python3.8 python3.8-dev python3.8-minimal
7 upgraded, 1 newly installed, 0 to remove and 123 not upgraded.
Need to get 10.8 MB of archives.
After this operation, 37.9 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Ign:1 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 python3.8-dev amd64 3.8.10-0ubuntu1~20.04.5
Ign:2 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 python3.8 amd64 3.8.10-0ubuntu1~20.04.5
Ign:3 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8-dev amd64 3.8.10-0ubuntu1~20.04.5
Ign:4 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8 amd64 3.8.10-0ubuntu1~20.04.5
Ign:5 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8-stdlib amd64 3.8.10-0ubuntu1~20.04.5
Ign:6 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 python3.8-minimal amd64 3.8.10-0ubuntu1~20.04.5
Ign:7 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8-minimal amd64 3.8.10-0ubuntu1~20.04.5
Ign:8 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 python3.8-venv amd64 3.8.10-0ubuntu1~20.04.5
Err:1 http://security.ubuntu.com/ubuntu focal-updates/main amd64 python3.8-dev amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
Err:2 http://security.ubuntu.com/ubuntu focal-updates/main amd64 python3.8 amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
Err:3 http://security.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8-dev amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
Err:4 http://security.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8 amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
Err:5 http://security.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8-stdlib amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
Err:6 http://security.ubuntu.com/ubuntu focal-updates/main amd64 python3.8-minimal amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
Err:7 http://security.ubuntu.com/ubuntu focal-updates/main amd64 libpython3.8-minimal amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
Err:8 http://security.ubuntu.com/ubuntu focal-updates/universe amd64 python3.8-venv amd64 3.8.10-0ubuntu1~20.04.5
404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.8/python3.8-dev_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.8/python3.8_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.8/libpython3.8-dev_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.8/libpython3.8_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.8/libpython3.8-stdlib_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.8/python3.8-minimal_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/main/p/python3.8/libpython3.8-minimal_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/universe/p/python3.8/python3.8-venv_3.8.10-0ubuntu1~20.04.5_amd64.deb 404 Not Found [IP: 91.189.91.38 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Ran
apt-get update && apt-get upgrade
, and tried again to run/mnt/c/SysGCC/esp32/esp-idf/v5.0/install.sh
It seemed to be successful, so I tried to build:
-- Building ESP-IDF components for target esp32
CMake Error at /mnt/c/SysGCC/esp32/esp-idf/v5.0/tools/cmake/build.cmake:519 (message):
usage: __main__.py [-h] [--project_dir PROJECT_DIR]
[--interface_version {0,1}]
{prepare_dependencies,inject_requirements,inject_requrements}
...
__main__.py: error: argument --interface_version: invalid int value: ''
Call Stack (most recent call first):
/mnt/c/SysGCC/esp32/esp-idf/v4.4.2/tools/cmake/project.cmake:384 (idf_build_process)
CMakeLists.txt:59 (project)
-- Configuring incomplete, errors occurred!
After all this, I tried to load a know-working project in v4.4.2 and simply change to v5. I see this error in Visual Studio:
ESP-IDF path changed from C:\SysGCC\esp32\esp-idf\v4.4.2 to C:\SysGCC\esp32\esp-idf\v5.0. Deleting C:\workspace\wolfssl-bandi13\IDE\Espressif\ESP-IDF\examples\wolfssl_benchmark\build\VisualGDB\Debug...
Running CMake: C:\Users\gojimmypi\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G "Ninja" -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=c:/sysgcc/esp32/tools/ninja/1.10.2/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0 -DIDF_TARGET=esp32
-- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.38.1.windows.1")
-- The C compiler identification is GNU 8.4.0
-- The CXX compiler identification is GNU 8.4.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/SysGCC/esp32/tools/xtensa-esp32-elf/esp-2021r2-patch3/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc.exe
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/SysGCC/esp32/tools/xtensa-esp32-elf/esp-2021r2-patch3/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: C:/SysGCC/esp32/tools/xtensa-esp32-elf/esp-2021r2-patch3/xtensa-esp32-elf/bin/xtensa-esp32-elf-g++.exe - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32
-- Checking Python dependencies...
Python requirements are satisfied.
Constraint file: C:\Users\gojimmypi\.espressif\espidf.constraints.v5.0.txt
Requirement files:
- C:\SysGCC\esp32\esp-idf\v5.0\tools\requirements\requirements.core.txt
Python being checked: C:\Users\gojimmypi\.espressif\python_env\idf5.0_py3.8_env\Scripts\python.exe
-- Configuring incomplete, errors occurred!
CMake Error at C:/SysGCC/esp32/esp-idf/v5.0/tools/cmake/build.cmake:519 (message):
C:\SysGCC\esp32\esp-idf\v5.0\python-env\Scripts\python.exe: Error while
finding module specification for 'idf_component_manager.prepare_components'
(ModuleNotFoundError: No module named 'idf_component_manager')
Call Stack (most recent call first):
C:/SysGCC/esp32/esp-idf/v5.0/tools/cmake/project.cmake:440 (idf_build_process)
CMakeLists.txt:12 (project)
See also "C:/workspace/wolfssl-bandi13/IDE/Espressif/ESP-IDF/examples/wolfssl_benchmark/build/VisualGDB/Debug/CMakeFiles/CMakeOutput.log".
System.Exception: CMake exited with code 1
at e43.l(n b, Object a)
========== Project Configuration Summary ==========
VisualGDB_wolfssl_benchmark configured in 00:08
========== Configuration: 1 Succeeded, 0 Failed, 0 Skipped ==========
I’ve otherwise had great success with prior versions of the ESP-IDF in VisualGDB.
I’m using Visual Studio 2019 16.11.21 and VisualGDB 5.6R9 (build 4769)
Please advise the exact steps that are needed to properly install Espressif ESP-IDF v5 support. Thank you.
Attachments:
You must be logged in to view attached files.December 22, 2022 at 08:40 #33591gojimmypiParticipantHey @PaulMartinsen and others interested in the ESP-IDF v5: there was a new offline IDF release overnight. Unfortunately still called “5.0”
Release Release offline-5.0 · espressif/idf-installer (github.com)
I’m not sure if this is referenced directly by the VisualGDB toolchain install, or if a copy is used.
Also: see this link regarding <a class=”Link–secondary markdown-title” title=”Tools: bugfix wrong format of idf-env.json, KeyError: ‘idfSelectedId’
Closes https://github.com/espressif/esp-idf/issues/9837″ href=”https://github.com/espressif/esp-idf/commit/77569c24b98401083f936599e4c94950867a2e22″ data-pjax=”true”>KeyError: ‘idfSelectedId’ if anyone other than me also uses the VisualGDB toolchains to test from DOS/Linux(WSL)
https://github.com/espressif/esp-idf/issues/9837#issuecomment-1362618035
December 22, 2022 at 10:17 #33594supportKeymasterHi All,
@angel, @paulmartinsen – please make sure you use the latest VisualGDB 5.6R9. The older versions indeed do not support the new Python environment layout introduced in ESP-IDF 5.0 and will require manual setup.
@gojimmypi – please do read this reply. You keep doing multiple things at one and breaking them further and further. If you would like to get anything working, we urge you to read and follow the best engineering practices described here. -
AuthorPosts
- You must be logged in to reply to this topic.