Espressif ESP-IDF 5.5 Requires Python 3.9 or newer

Sysprogs forums Forums VisualGDB Espressif ESP-IDF 5.5 Requires Python 3.9 or newer

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #36240
    gojimmypi
    Participant

    Hi.

    I’m trying to use the latest GitHub version of the Espressif ESP-IDF. (version 5.5, not released yet) to test the latest release of wolfSSL.

    I know that pre-release versions of the ESP-IDF are not supported here, but I was still hoping for some tips on where and how python versions are detected in VisualGDB.

    The problem occurs when I “Reload cmake project” using the latest ESP-IDF. A dialog box pops up indicating:

    The selected ESP-IDF checkout requires a Python environment in C:\SysGCC\esp32-master\python_env\\idf.5_py3.8_env. Would you like to create i automatically?

    When I click “Yes”, I see another dialog box indicating “Failed to initialize virtual python environment”  and “Python.exe exited with error code 1”

    Run “C:\Users\gojimmypi\AppData\Local\VisualGDB\Python-3.8.10\python.exe C:\SysGCC\esp32\esp-idf\master\tools\idf_tools.py install-python-env” in directory “” on local computer
    ————————–
    ESP-IDF supports Python 3.9 or newer but you are using Python 3.8.10. Please upgrade your installation as described in the documentation.
    ————————–
    Command exited with code 1

    I tried to manually run this from command line:

    C:\Users\gojimmypi\AppData\Local\VisualGDB\Python-3.11.5\python.exe C:\SysGCC\esp32\esp-idf\master\tools\idf_tools.py install-python-env

    Although a new target directory was created, VisualGDB does not see it. I continued to receive the error noted above.

    I do have a more recent version of Python installed. From a fresh DOS prompt:

    python --version
    Python 3.11.9

    The SysGCC directories otherwise seem to be working properly from a command prompt. I can compile from command-line in both Windows DOS and WSL using the sysgcc directories and the very latest version of the ESP-IDF.

    I’m using Visual Studio 2022 v17.11.5

    I’ve been putting off updating VisualGDB automatically from within Visual Studio, but earlier today I manually downloaded and installed version 6.0R6 (build 5262).

    I tried restarting Visual Studio and even rebooting.

    Any tips on resolving this will be appreciated. Thank you.

    #36749
    gojimmypi
    Participant

    Heads up the Espressif ESP-IDF v5.5 is now in beta:

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

    I was initially unable to get VisualGDB to use the new toolchain for the same cmake version issue described in my original message.

    However, I found this topic from last year: “Problem on new ESP32 toolchain”:

    https://sysprogs.com/w/forums/topic/problem-on-new-esp32-toolchain/

    Specifically the link to “Troubleshooting”:

    https://visualgdb.com/documentation/espidf/#troubleshooting

    To resolve, I set my Tools – Options – VisualGDB – General – Python Directory (ESP-IDF) to

    C:\Users\gojimmypi\AppData\Local\VisualGDB\Python-3.11.5

     

    Screen snip of python directory setting

     

     

    • This reply was modified 3 months ago by gojimmypi.
    #36821
    gojimmypi
    Participant

    Heads up ESP-IDF v5.5 has been released.

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

    Beware:  “Release v5.5 is mostly compatible with apps written for ESP-IDF v5.4.”

    See the section: “breaking changes”

    • This reply was modified 1 month, 4 weeks ago by gojimmypi.
    #36883
    support
    Keymaster

    OK, good news for all ESP32 users. We have looked into the tool structure used by the Espressif’s VS Code extension, and they look very solid and well-organized.

    So, we updated VisualGDB to directly use exactly the same packages that the VS Code extension does, and hence produce exactly the same results. You no longer need to wait for an updated toolchain from us; any IDF/ADF version from Espressif that works with VS Code now also works with VisualGDB out-of-the-box, producing exactly the same results.

    You would need to update to the latest VisualGDB 6.1 Beta 1 in order to use the new setup.

    We also published a detailed documentation page on the new project structure here: https://visualgdb.com/documentation/espidf/consolidated/

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.