CLion
 
2022.3
Shortcuts: Windows
Get CLion
You are viewing the documentation for an earlier version of CLion.
  1. Language and framework-specific guidelines
  2. ESP-IDF

ESP-IDF

Last modified: 11 January 2023

ESP-IDF is the official development framework for the ESP32 and ESP32-S Series SoCs. This article is an introductory guide for working with ESP-IDF in CLion.

Some steps replicate the ESP-IDF Get Started guide. Examples below are given for the case of macOS, Windows-specific instructions are marked accordingly.

Prepare the environment

  1. Make sure you have a recent Python version, pip, and git installed on your system.

  2. Using your system terminal, create a directory for ESP-IDF and clone the official repository: 

    mkdir -p ~/esp
cd ~/esp
git clone --recursive https://github.com/espressif/esp-idf.git

    ESP-IDF will be downloaded into ~/esp/esp-idf.

  3. In the same shell, install the tools: 

    cd ~/esp/esp-idf
./install.sh

  4. On Windows, make sure the USB bridge of the ESP-32 board is identified correctly. You can check that in the Device Manager.

    tip

    Watch Developing for ESP32 With CLion on Windows: Preparation for video instructions.

Configure an ESP CMake project in CLion

Toolchain on Windows

Open the Hello-world project

  1. Go to File | Open and select the examples/get-started/hello_world folder.

  2. Click Open as Project and trust the sources.

    At this point, project loading might fail.

Configure environment variables

Next, set up the required environment variables.

note

Starting from the 2021.3 version of CLion, it is possible to initialize the environment via a script. Instructions below will be updated shortly.

For video instructions, watch Developing for ESP32 With CLion on Windows: Setting up a project in CLion.

  1. Go to Settings | Build, Execution, Deployment | CMake and use the Environment field to add a new variable called IDF_PATH.

    Set the value to the esp-idf folder path, which you can copy from the terminal.

  2. After adding the IDF_PATH variable, CMake load might still fail due to certain Python dependencies being missed. In this case, adjust the PATH variable to include all entries pointing to the .espressif folder.

    1. Switch back to the terminal and run echo %PATH%.

    2. Copy everything that contains the .espressif folder.

    3. Navigate to CMake settings again, open the Environment field, and find PATH in the list of system variables.

    4. Prepend the value with what you have just copied. Make sure there is a semicolon at the end of the paste.

    Environment variables for CMake

  3. Call Tools | CMake| Reset Cache and Reload Project from the main menu. Project loading should perform successfully.

Build the project

  1. CLion will automatically create run/debug configurations for all the detected CMake targets.

    To build the project, select app in the configuration switcher, then click the hammer icon or press Ctrl + F9 to run build for this configuration.

  2. At this point, all CLion code insight features are available for your ESP project. Watch Developing for ESP32 With CLion on Windows: Code insight for some examples.

Flashing and monitoring an ESP-32 chip in CLion

tip

For video instructions, watch Developing for ESP32 With CLion on Windows: Flashing and monitoring your ESP-32 chip

  1. Select flash in the configuration switcher and click the hammer icon or press Ctrl + F9 to build it.

    In the build output, you can check the percentage indicator for chip flashing.

  2. Select the monitor configuration and build it. If you get an error that serial port can not be opened, then do the following:

    1. Open the Device Manager and check the port that is used by your ESP device.

    2. Add one more variable to the Environment variables in CMake settings: ESPPORT. Set the value to the port, for example, COM3.

    3. After the project is reloaded, build the monitor configuration again. The ESP-32 chip should report back as expected.

Known issues and limitations

  • There's a feature request for the ability to initialize toolchain environment via a script.

  • Currently, the size of long is considered 64-bit, while there should be 32-bit for ESP-32 (CPP-23731). To workaround this, go to File | Settings | Languages & Frameworks | C/C++ | Clangd and add --target=riscv32 to the clangd diagnostics options.

Troubleshooting (Windows)

If you are getting the Git executable not found error on Windows, make sure that Git is installed into a location discoverable by ESP-IDF's find_package(Git) command.

To workaround that, add the GIT environment variable with the full path to the git.exe binary. You can do that by modifying esp/idf/tools/cmake/git_submodules.cmake. In the first line, change find_package(Git) to the following:

if (DEFINED ENV{GIT})
    execute_process(COMMAND $ENV{GIT} --version
    OUTPUT_VARIABLE git_version
    ERROR_QUIET
    OUTPUT_STRIP_TRAILING_WHITESPACE)
    if (git_version MATCHES "^git version [0-9]")
        string(REPLACE "git version " "" GIT_VERSION_STRING "${git_version}")
        set(GIT_FOUND True)
        set(GIT_EXECUTABLE $ENV{GIT})
    endif()
    unset(git_version)
else()
    find_package(Git)
endif ()

See also

External Links