[js]

thank you for the help and clarification.

I did manage to get a setup running with 5.2 and 5.4 gnu toolchain now. The older projects i will attempt to migrate or see if I can boot up a VM somehow.

[js]

i cannot get the consolidated toolchain too work.

I attempted with the packaged gnu toolchain

I tried with combination of visual studio 2022, visualgdb 6.1 and the IDF 5.1; esp32-20230208 gnu toolchain, on windows 11 Pro 25H2

my installation root of this toolchain is “C:\SysGCC\esp32__V5_1__GCC_12_2_0” (not the expected default esp32 folder, is this somehow important)

• helloworld project, failed with error similar to the one in my first post
• existing original project from me, failed with error similar to the one in my first post

this is after two consecutive reinstalls of all these tools mentioned. on a fresh machine. How can I solve this? Is the packaged toolchain not supposed to decouple from rapid tooling changes? and how can it still miss dependencies? this is the message explaining where it failed
C:\Users\Beheerder\AppData\Local\VisualGDB\Python-3.8.10\include\pyconfig.h(59): fatal error C1083: Cannot open include file: ‘io.h’: No such file or directory

do i need to install python myself and point it towards that installation? im not sure and could not find any conclusive

This is a weird and really unexpected problem, since I wish to evaluate going further with visualgdb (had good experience with this toolchain on my previous machine, where it all worked very well) and i did not expect too be stuck in the basic installation

from the first error message i notice

 

[js]

i cannot open any visual gdb project made prior to consolidated toolchain

i cannot start a new project from any branch from consolidated toolchain

documentation seems straightforward but it is not and seem easy to miss something important

[js]

i did the following:

• opened an old project on release/v5.1 in visual studio 2022, this is broken since no old toolchain has ever been completed successful
• I found the v5.1 branch in the espressif github and managed to install the consolidated toolchain for this release;
• Then in the project properties i was able to change the project to this consolidated toolchain
• when reopening this project in vs it picked up the change, asked me to retarget to v5.1.1 and building failed

Removing C:\Users\Beheerder\Documents\Espressif\Solutions\CP719\CP719_1/build/VisualGDB/Debug…
Run “C:\Users\Beheerder\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/Users/Beheerder/.espressif/tools/ninja/1.12.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0″ in directory “C:\Users\Beheerder\Documents\Espressif\Solutions\CP719\CP719_1/build/VisualGDB/Debug” on local computer
C:\Users\Beheerder\AppData\Local\VisualGDB\CMake\bin\cmake.exe ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/Users/Beheerder/.espressif/tools/ninja/1.12.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0
— IDF_TARGET is not set, guessed ‘esp32’ from sdkconfig ‘C:/Users/Beheerder/Documents/Espressif/Solutions/CP719/CP719_1/sdkconfig’
— Found Git: C:/Users/Beheerder/.espressif/tools/idf-git/2.39.2/cmd/git.exe (found version “2.39.2.windows.1”)
— The C compiler identification is GNU 12.2.0
— The CXX compiler identification is GNU 12.2.0
— The ASM compiler identification is GNU
— Found assembler: C:/Users/Beheerder/.espressif/tools/xtensa-esp32-elf/esp-12.2.0_20230208/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:/Users/Beheerder/.espressif/tools/xtensa-esp32-elf/esp-12.2.0_20230208/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:/Users/Beheerder/.espressif/tools/xtensa-esp32-elf/esp-12.2.0_20230208/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…
pkg_resources cannot be imported. The most common cause is a missing pip or setuptools package. If you’ve installed a custom Python then these packages are provided separately and have to be installed as well. Please refer to the Get Started section of the ESP-IDF Programming Guide for setting up the required packages.
Constraint file: C:\Users\Beheerder\.espressif\espidf.constraints.v5.1.txt
Requirement files:
– C:\Users\Beheerder\esp-idf\v5.1\esp-idf\tools\requirements\requirements.core.txt
Python being checked: C:\Users\Beheerder\.espressif\python_env\\idf5.1_py3.11_env\Scripts\python.exe
CMake Error at C:/Users/Beheerder/esp-idf/v5.1/esp-idf/tools/cmake/build.cmake:366 (message):
Failed to run Python dependency check. Python: python, Error: -1
Call Stack (most recent call first):
C:/Users/Beheerder/esp-idf/v5.1/esp-idf/tools/cmake/build.cmake:498 (__build_check_python)
C:/Users/Beheerder/esp-idf/v5.1/esp-idf/tools/cmake/project.cmake:464 (idf_build_process)
CMakeLists.txt:8 (project)

— Configuring incomplete, errors occurred!
————————————————————-
Command exited with code 1
Executable: C:\Users\Beheerder\AppData\Local\VisualGDB\CMake\bin\cmake.exe
Arguments: ../../.. -G “Ninja” -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_MAKE_PROGRAM=C:/Users/Beheerder/.espressif/tools/ninja/1.12.1/ninja.exe -DESP_PLATFORM=1 -DCCACHE_ENABLE=0
Directory: C:\Users\Beheerder\Documents\Espressif\Solutions\CP719\CP719_1/build/VisualGDB/Debug
Command-line action failed

========== Project Rebuild Summary ==========
CP719_1 rebuilt in 00:05
========== Rebuild: 0 Succeeded, 1 Failed, 0 Skipped ==========

im confused, the gui to download all this told me the python requirement is satisfied (python 3.11) but it still complaining, do I install python separate as well?

[js]

my project type is an ESP-IDF project

[js]

thank you very much, debugging and halting works now. Since this was done on a throwaway project and I started an actual project (with default settings) where I don’t see this error, i consider this solved.

[js]

thank you, with the above I was able to launch debug session and halting on breakpoint. It throws an error message before i can run but i am able to reach the entry point and start/run the program,

i attached a screenshot of the error message that pops up before I start running. Could you perhaps elaborate on it? Could it be an indication of things set up wrong?

If i have to guess, it looks like something expects the stack to grow down in the address range ? but detects that in this case it is not? I dont have much familiarity with the chip yet at that level of detail and I try to leave the datasheet closed as long as possible  =D

have a nice day, so far I like the tool and hope I can continue with it.

Attachments:

You must be logged in to view attached files.

[js]

i really dont understand this process,

first, early debug session (that i did not correctly capture with the logs) succesfully uploaded the firmware image to the target, and the blink project made my gpio pin blink correctly. Doing break all gave me the following error:

Frame not in module
The current stack frame was not found in a loaded module. Source cannot be shown for this location.

I instrumented that gdb log after that and since then i cannot succesfully get the blink project to run. The upload itself seems fine but when i reset the target, it goes to an undefined area in the chip, i guess. I attached that specific log, maybe there is already indication what i do wrong?

FYI, i upload via jtag as well, for that i have to boot into the programmer mode (with the BOOT/RESET combo).

Attachments:

You must be logged in to view attached files.

[Author]

Posts