[gojimmypi]

I 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

[gojimmypi]

The 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 in C:\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.

[gojimmypi]

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)

 

• This reply was modified 1 year, 4 months ago by gojimmypi.
• This reply was modified 1 year, 4 months ago by gojimmypi.
• This reply was modified 1 year, 4 months ago by gojimmypi.

[gojimmypi]

Tada! ESP-IDF Version 5.0 is released 🙂

https://github.com/espressif/esp-idf/releases/tag/v5.0

[gojimmypi]

Heads up there’s finally an ESP-IDF 5.0 Release Candidate! Woohoo!  😎

Release ESP-IDF Pre-release v5.0-rc1 · espressif/esp-idf · GitHub

[gojimmypi]

Hello!

Just a little heads-up that ESP-IDF V5 is in release beta.  😎

https://github.com/espressif/esp-idf/releases

https://docs.espressif.com/projects/esp-idf/en/v5.0-beta1/esp32/

Hopefully final release any day now.

Cheers

 

[gojimmypi]

hi @sve-jvi,

you may be interested in this esp-idf-v5 issue on this forum, and Espressif idf-installer issue #143 on GitHub.

I’m certainly interested if you make any progress.

[gojimmypi]

Hi,

Hopefully Espressif will have an official release of ESP-IDF V5 soon.

Manually editing the toolchain.xml and bsp.xml was marginally successful, but there’s a new error related to kconfiglib.that I’ve been unable to resolve.

Although there’s a line:

    Requirement already up-to-date: kconfiglib

There’s still an error:

  ModuleNotFoundError: No module named 'kconfiglib'

Full log:

Executing pre-build actions
Run "pip3 install --upgrade kconfiglib" in directory "C:\Users\gojimmypi\source\repos\EmbeddedProject23" on local computer
pip3 install --upgrade kconfiglib
Requirement already up-to-date: kconfiglib in c:\users\gojimmypi\appdata\local\programs\python\python38-32\lib\site-packages (14.1.0)
WARNING: You are using pip version 19.2.3, however version 22.2.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
Run "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" in directory "C:\Users\gojimmypi\source\repos\EmbeddedProject23/build/VisualGDB/Debug" on local computer
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
-- Project is not inside a git repository, or git repository has no commits; will not use 'git describe' to determine PROJECT_VER.
-- Building ESP-IDF components for target esp32
-- Checking Python dependencies...
Python requirements are satisfied.
Skipping the download of C:\Users\gojimmypi\.espressif\espidf.constraints.v5.0.txt because it was downloaded recently. If you believe that this is causing you trouble then remove it manually and re-run your install script.
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
-- Project sdkconfig file C:/Users/gojimmypi/source/repos/EmbeddedProject23/sdkconfig
Traceback (most recent call last):
File "C:/SysGCC/esp32/esp-idf/v5.0/tools/kconfig_new/confgen.py", line 23, in <module>
import gen_kconfig_doc
File "C:\SysGCC\esp32\esp-idf\v5.0\tools\kconfig_new\gen_kconfig_doc.py", line 27, in <module>
import kconfiglib
ModuleNotFoundError: No module named 'kconfiglib'
CMake Error at C:/SysGCC/esp32/esp-idf/v5.0/tools/cmake/kconfig.cmake:176 (message):
Failed to run confgen.py
(python;C:/SysGCC/esp32/esp-idf/v5.0/tools/kconfig_new/confgen.py;--list-separator=semicolon;--kconfig;C:/SysGCC/esp32/esp-idf/v5.0/Kconfig;--sdkconfig-rename;C:/SysGCC/esp32/esp-idf/v5.0/sdkconfig.rename;--config;C:/Users/gojimmypi/source/repos/EmbeddedProject23/sdkconfig;--env-file;C:/Users/gojimmypi/source/repos/EmbeddedProject23/build/VisualGDB/Debug/config.env).
Error 1
Call Stack (most recent call first):
C:/SysGCC/esp32/esp-idf/v5.0/tools/cmake/build.cmake:596 (__kconfig_generate_config)
C:/SysGCC/esp32/esp-idf/v5.0/tools/cmake/project.cmake:434 (idf_build_process)
CMakeLists.txt:8 (project)


-- Configuring incomplete, errors occurred!
See also "C:/Users/gojimmypi/source/repos/EmbeddedProject23/build/VisualGDB/Debug/CMakeFiles/CMakeOutput.log".
-------------------------------------------------------------
Command exited with code 1
Executable: C:\Users\gojimmypi\AppData\Local\VisualGDB\CMake\bin\cmake.exe
Arguments: ../../.. -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
Directory: C:\Users\gojimmypi\source\repos\EmbeddedProject23/build/VisualGDB/Debug
Command-line action failed

========== Project Build Summary ==========
EmbeddedProject23 built in 00:14
========== Build: 0 Succeeded, 1 Failed, 0 Skipped ==========

 

[gojimmypi]

I’ve made some progress on getting the emitted VisualGDB cmake command to complete without errors, at least from a command prompt.

For one, I needed to add 2 CMake config variables in the Build Settings GUI:

IDF_TARGET = esp32c3
CCACHE_ENABLE = 1

Next, I needed to add these environment variables:

SET IDF_CCACHE_ENABLE=1
SET IDF_PATH=C:\SysGCC\esp32\esp-idf\v5.0
SET IDF_PYTHON_ENV_PATH=C:\Espressif\python_env\idf5.0_py3.8_env
SET IDF_TOOLS_PATH=C:\Espressif
SET ESP_IDF_VERSION=5.0

And last, I needed to add these to the Path:

C:\Espressif\tools\xtensa-esp-elf-gdb\11.2_20220529\xtensa-esp-elf-gdb\bin;
C:\Espressif\tools\riscv32-esp-elf-gdb\11.2_20220529\riscv32-esp-elf-gdb\bin;
C:\Espressif\tools\xtensa-esp32-elf\esp-2022r1-RC1-11.2.0\xtensa-esp32-elf\bin;
C:\Espressif\tools\xtensa-esp32s2-elf\esp-2022r1-RC1-11.2.0\xtensa-esp32s2-elf\bin;
C:\Espressif\tools\xtensa-esp32s3-elf\esp-2022r1-RC1-11.2.0\xtensa-esp32s3-elf\bin;
C:\Espressif\tools\riscv32-esp-elf\esp-2022r1-RC1-11.2.0\riscv32-esp-elf\bin;
C:\Espressif\tools\esp32ulp-elf\2.28.51-esp-20191205\esp32ulp-elf-binutils\bin;
C:\Espressif\tools\esp32s2ulp-elf\2.28.51-esp-20191205\esp32s2ulp-elf-binutils\bin;
C:\Espressif\tools\openocd-esp32\v0.11.0-esp32-20220411\openocd-esp32\bin;
C:\Espressif\tools\ninja\1.10.2\;C:\Espressif\tools\idf-exe\1.0.3\;
C:\Espressif\tools\ccache\4.3\ccache-4.3-windows-64;
C:\Espressif\tools\dfu-util\0.9\dfu-util-0.9-win64;
C:\Espressif\python_env\idf5.0_py3.8_env\Scripts;
C:\SysGCC\esp32\esp-idf\v5.0\tools;C:\Python36\;
C:\Python36\Scripts;

What is the best method for modifying the path and environment variables for CMake in VisualGDB? I saw the documentation, but I don’t know exactly where to apply that. Before I go pecking them all in, is that the “User Variables” at the bottom of the config page?

btw – I tried simply adding a called to export.bat in the “before build”… but it does exactly that: before the build, but not before cmake.

Thank you.

 

[gojimmypi]

Hi.

Yes, I completely understand. That’s fair.

I’m still hopeful that I can get this working. 🙂

I have it working using idf.py, and this text seems to indicate it should be possible:

Any project that can be built via ESP-IDF tools, can also be built with VisualGDB

I’ve opened Espressif idf-installer issue #142 in the hope that someone has an idea for a solution.

[gojimmypi]

I also encountered this error with File-New Project:  I didn’t notice that the main() lived in a file with only a .c extension.

Can’t call C++ from a .c file, but oddly the compile error was on the target class file with the .cpp, not the main file.

Error Failed to compile IoT_BBQ_STM32.c. arm-none-eabi-gcc.exe exited with code 1
Error unknown type name 'class'
Error expected '=', ',', ';', 'asm' or '__attribute__' before '{' token

 

[gojimmypi]

After adding my support ticket regarding the Prerelease 1 ESP-IDF support I noticed this topic is fairly similar – in particular the  problem with include files. Although I too, am very interested in the Arduino library support, I’ve created a sample project showing that the include file feature is in general not working as intuitively as one might expect. For more info – see this sample on GitHub:

https://github.com/gojimmypi/EmbeddedProject8

Perhaps this is a feature request: to honor the Project Properties “Additional Include Files” – instead of adding as components? (although I’ve also not been able to successfully add the sample TestLibrary as a component, either.

[gojimmypi]

actually, I do know how to build them: the project builds fine in Linux. 🙂 As for Windows, I’ve been programming in Visual Studio a long time, but I’ve never once have taken a solution developed there – and compiled it from command line.  To take something like VisualGDB project in Visual Studio and compile that from command line, seems rather complex.  Addicted to IDE’s I guess. 😉  (not always a great thing to not understand the whole process when insulated with an IDE, I know).

If I had the ability to build this project on manually on Windows before import, well, I kinda would not need to import to Visual Studio. I do agree that would be useful. But I was hoping to avoid the hassle of setting up the toolchain since I thought that’s what VisualGDB import wizard would do for me.

It would be cool if VisualGDB helped with that import process, and used the toolchain specified in the wizard. But ya, I understand given an arbitrary makefile, that’s probably not a trivial process to convert. Too bad, as that would be really awesome.

fwiw – I was able to get Windows-based debugging working from VSCode (of all places!). I compile on Linux, use OpenOCD there, but connect using the VSCode GDB. It is really quite awesome:

https://gojimmypi.blogspot.com/2017/05/vscode-remote-debugging-of-embedded.html

VSCode shockingly does many of the debugging things that Visual Studio does (single step, hover text for variable values, intellisense, peek definition, and more)

Cheers

[gojimmypi]

Hi.

That sounds like a good suggestion. Could you give a little more detail on just how to do that? I guess I’ve grown so used to Visual Studio IDE right-click builds, that I’ don’t know how to do it manually from command-line. I went back to a known-good VisualGDB project that works and compiles – and even there have not been able to figure out the command-line method. I tried simply “make” from the solution and project directories… that of course returned the same “make: *** No targets specified and no makefile found.  Stop.” error.

 

[gojimmypi]

Thanks for the verification. Hopefully Visual Studio 2017 will be fixed soon. In the meantime I tried your advice with Visual Studio 2015:

Microsoft Visual Studio Enterprise 2015
Version 14.0.25431.01 Update 3
Microsoft .NET Framework
Version 4.6.01586

It does not explode, but it also does not compile. I added a few new pics here:

https://gojimmypi.blogspot.com/2017/05/converting-opendps-to-visual-studio.html

The problem appears to be the config generated:  “make: *** No targets specified and no makefile found. Stop”

The resultant build config was “win32″… so I tried both creating an “ARM” as well as “VisualGDB” config, but no luck. I then tried to “convert to stand alone project”. As expected, no change to the missing make target.

I am not familiar with VisualGDB on manually setting make targets (I would have hoped the wizard would have done that for me).

I also tried the “Project – Add VisualGDB configuration – new Windows configuration” – resulting in “Creating Windows Configuration is only supported for Windows, Linux, and native visual c++ projects”

I’ve not been able to find any documentation or perhaps a tutorial on converting existing projects… could you kindly point me in the right direction? thanks 🙂

 

 

[Author]

Posts