Downloadable Tools¶
ESP-IDF build process relies on a number of tools: cross-compiler toolchains, CMake build system, and others.
Installing the tools using an OS-specific package manager (like apt, yum, brew, etc.) is the preferred method when the required version of the tool is available. This recommendation is reflected in the Getting Started guide. For example, on Linux and macOS it is recommended to install CMake using an OS package manager.
However, some of the tools are IDF-specific and are not available in OS package repositories. Furthermore, different versions of ESP-IDF require different versions of the tools to operate correctly. To solve these two problems, ESP-IDF provides a set of scripts for downloading and installing the correct versions of tools, and exposing them in the environment.
The rest of the document refers to these downloadable tools simply as “tools”. Other kinds of tools used in ESP-IDF are:
Python scripts bundled with ESP-IDF (such as
idf.py
)Python packages installed from PyPI.
The following sections explain the installation method, and provide the list of tools installed on each platform.
Note
This document is provided for advanced users who need to customize their installation, users who wish to understand the installation process, and ESP-IDF developers.
If you are looking for instructions on how to install the tools, see the Getting Started Guide.
Tools metadata file¶
The list of tools and tool versions required for each platform is located in tools/tools.json. The schema of this file is defined by tools/tools_schema.json.
This file is used by tools/idf_tools.py script when installing the tools or setting up the environment variables.
Tools installation directory¶
IDF_TOOLS_PATH
environment variable specifies the location where the tools are to be downloaded and installed. If not set, IDF_TOOLS_PATH
defaults to HOME/.espressif
on Linux and macOS, and %USER_PROFILE%\.espressif
on Windows.
Inside IDF_TOOLS_PATH
, the scripts performing tools installation create the following directories:
dist
— where the archives of the tools are downloaded.tools
— where the tools are extracted. The tools are extracted into subdirectories:tools/TOOL_NAME/VERSION/
. This arrangement allows different versions of tools to be installed side by side.
GitHub Assets Mirror¶
Most of the tools downloaded by the tools installer are GitHub Release Assets, which are files attached to a software release on GitHub.
If GitHub downloads are inaccessible or slow to access, it’s possible to configure a GitHub assets mirror.
To use Espressif’s download server, set the environment variable IDF_GITHUB_ASSETS
to dl.espressif.com/github_assets
. When the install process is downloading a tool from github.com
, the URL will be rewritten to use this server instead.
Any mirror server can be used provided the URL matches the github.com
download URL format: the install process will replace https://github.com
with https://${IDF_GITHUB_ASSETS}
for any GitHub asset URL that it downloads.
Note
The Espressif download server doesn’t currently mirror everything from GitHub, it only mirrors files attached as Assets to some releases as well as source archives for some releases.
idf_tools.py
script¶
tools/idf_tools.py script bundled with ESP-IDF performs several functions:
install
: Download the tool into${IDF_TOOLS_PATH}/dist
directory, extract it into${IDF_TOOLS_PATH}/tools/TOOL_NAME/VERSION
.install
command accepts the list of tools to install, inTOOL_NAME
orTOOL_NAME@VERSION
format. Ifall
is given, all the tools (required and optional ones) are installed. If no argument orrequired
is given, only the required tools are installed.download
: Similar toinstall
but doesn’t extract the tools. An optional--platform
argument may be used to download the tools for the specific platform.export
: Lists the environment variables which need to be set to use the installed tools. For most of the tools, settingPATH
environment variable is sufficient, but some tools require extra environment variables.The environment variables can be listed in either of
shell
orkey-value
formats, set by--format
parameter:shell
produces output suitable for evaluation in the shell. For example,export PATH="/home/user/.espressif/tools/tool/v1.0.0/bin:$PATH"
on Linux and macOS, and
set "PATH=C:\Users\user\.espressif\tools\v1.0.0\bin;%PATH%"
on Windows.
Note
Exporting environment variables in Powershell format is not supported at the moment.
key-value
format may be used instead.The output of this command may be used to update the environment variables, if the shell supports this. For example:
eval $($IDF_PATH/tools/idf_tools.py export)
key-value
produces output in VARIABLE=VALUE format, suitable for parsing by other scripts:PATH=/home/user/.espressif/tools/tool/v1.0.0:$PATH
Note that the script consuming this output has to perform expansion of
$VAR
or%VAR%
patterns found in the output.
list
: Lists the known versions of the tools, and indicates which ones are installed.check
: For each tool, checks whether the tool is available in the system path and inIDF_TOOLS_PATH
.
Install scripts¶
Shell-specific user-facing scripts are provided in the root of ESP-IDF repository to facilitate tools installation. These are:
install.bat
for Windows Command Promptinstall.ps1
for Powershellinstall.sh
for Bash
Aside from downloading and installing the tools into IDF_TOOLS_PATH
, these scripts prepare a Python virtual environment, and install the required packages into that environment.
Export scripts¶
Since the installed tools are not permanently added into the user or system PATH
environment variable, an extra step is required to use them in the command line. The following scripts modify the environment variables in the current shell to make the correct versions of the tools available:
export.bat
for Windows Command Promptexport.ps1
for Powershellexport.sh
for Bash
Note
To modify the shell environment in Bash, export.sh
must be “sourced”: . ./export.sh
(note the leading dot and space).
export.sh
may be used with shells other than Bash (such as zsh). However in this case the IDF_PATH
environment variable must be set before running the script. When used in Bash, the script will guess the IDF_PATH
value from its own location.
In addition to calling idf_tools.py
, these scripts list the directories which have been added to the PATH
.
Other installation methods¶
Depending on the environment, more user-friendly wrappers for idf_tools.py
are provided:
IDF Tools installer for Windows can download and install the tools. Internally the installer uses
idf_tools.py
.Eclipse plugin for ESP-IDF includes a menu item to set up the tools. Internally the plugin calls
idf_tools.py
.Visual Studio Code extension for ESP-IDF includes an onboarding flow. This flow helps setting up the tools. Although the extension does not rely on
idf_tools.py
, the same installation method is used.
Custom installation¶
Although the methods above are recommended for ESP-IDF users, they are not a must for building ESP-IDF applications. ESP-IDF build system expects that all the necessary tools are installed somewhere, and made available in the PATH
.
List of IDF Tools¶
xtensa-esp32-elf¶
Toolchain for Xtensa (ESP32) based on GCC
License: GPL-3.0-with-GCC-exception
More info: https://github.com/espressif/crosstool-NG
Platform |
Required |
Download |
---|---|---|
linux-amd64 |
required |
SHA256: 674080a12f9c5ebe5a3a5ce51c6deaeffe6dfb06d6416233df86f25b574e9279 |
linux-armel |
required |
SHA256: 6771e011dffa2438ef84ff3474538b4a69df8f9d4cfae3b3707ca31c782ed7db |
linux-i686 |
required |
SHA256: 076b7e05304e26aa6ec105c9e0dc74addca079bc2cae6e42ee7575c5ded29877 |
macos |
required |
SHA256: 6845f786303b26c4a55ede57487ba65bd25737232fe6104be03f25bb62f4631c |
win32 |
required |
SHA256: 81cecd5493a3fcf2118977f3fd60bd0a13a4aeac8fe6760d912f96d2c34fab66 |
win64 |
required |
SHA256: 58419852fefb7111fdec056ac2fd7c4bd09c1f4c17610a761a97b788413527cf |
xtensa-esp32s2-elf¶
Toolchain for Xtensa (ESP32-S2) based on GCC
License: GPL-3.0-with-GCC-exception
More info: https://github.com/espressif/crosstool-NG
Platform |
Required |
Download |
---|---|---|
linux-amd64 |
required |
SHA256: 40fafa47045167feda0cd07827db5207ebfeb4a3b6b24475957a921bc92805ed |
linux-armel |
required |
SHA256: 6c1efec4c7829202279388ccb388e8a17a34464bc351d677c4f04d95ea4b4ce0 |
linux-i686 |
required |
SHA256: bd3a91166206a1a7ff7c572e15389e1938c3cdce588032a5e915be677a945638 |
macos |
required |
SHA256: fe19b0c873879d8d89ec040f4db04a3ab27d769d3fd5f55fe59a28b6b111d09c |
win32 |
required |
SHA256: d078d614ae864ae4a37fcb5b83323af0a5cfdbd8243607664becdd0f977a1e33 |
win64 |
required |
SHA256: 6ea78b72ec52330b69af91dbe6c77c22bdc827817f044aa30306270453032bb4 |
esp32ulp-elf¶
Toolchain for ESP32 ULP coprocessor
License: GPL-2.0-or-later
More info: https://github.com/espressif/binutils-esp32ulp
Platform |
Required |
Download |
---|---|---|
linux-amd64 |
required |
SHA256: 3016c4fc551181175bd9979869bc1d1f28fa8efa25a0e29ad7f833fca4bc03d7 |
linux-armel |
required |
SHA256: 88967c086a6e71834282d9ae05841ee74dae1815f27807b25cdd3f7775a47101 |
macos |
required |
SHA256: a35d9e7a0445247c7fc9dccd3fbc35682f0fafc28beeb10c94b59466317190c4 |
win32 |
required |
SHA256: bade309353a9f0a4e5cc03bfe84845e33205f05502c4b199195e871ded271ab5 |
win64 |
required |
SHA256: bade309353a9f0a4e5cc03bfe84845e33205f05502c4b199195e871ded271ab5 |
esp32s2ulp-elf¶
Toolchain for ESP32-S2 ULP coprocessor
License: GPL-2.0-or-later
More info: https://github.com/espressif/binutils-esp32ulp
Platform |
Required |
Download |
---|---|---|
linux-amd64 |
required |
SHA256: df7b2ff6c7c718a7cbe3b4b6dbcd68180d835d164d1913bc4698fd3781b9a466 |
linux-armel |
required |
SHA256: 893b213c8f716d455a6efb2b08b6cf1bc34d08b78ee19c31e82ac44b1b45417e |
macos |
required |
SHA256: 5a9bb678a5246638cbda303f523d9bb8121a9a24dc01ecb22c21c46c41184155 |
win32 |
required |
SHA256: 587de59fbb469a39f96168ae3eaa9f06b2601e6e0543c87eaf1bd97f23e5c4ca |
win64 |
required |
SHA256: 587de59fbb469a39f96168ae3eaa9f06b2601e6e0543c87eaf1bd97f23e5c4ca |
cmake¶
CMake build system
On Linux and macOS, it is recommended to install CMake using the OS-specific package manager (like apt, yum, brew, etc.). However, for convenience it is possible to install CMake using idf_tools.py along with the other tools.
License: BSD-3-Clause
More info: https://github.com/Kitware/CMake
Platform |
Required |
Download |
---|---|---|
linux-amd64 |
optional |
https://github.com/Kitware/CMake/releases/download/v3.16.4/cmake-3.16.4-Linux-x86_64.tar.gz SHA256: 12a577aa04b6639766ae908f33cf70baefc11ac4499b8b1c8812d99f05fb6a02 |
linux-armel |
optional |
https://dl.espressif.com/dl/cmake/cmake-3.20.3-Linux-armv7l.tar.gz SHA256: f8bd050c2745f0dcc4b7cef9738bbfef775950a10f5bd377abb0062835e669dc |
macos |
optional |
https://github.com/Kitware/CMake/releases/download/v3.16.4/cmake-3.16.4-Darwin-x86_64.tar.gz SHA256: f60e0ef96da48725cd8da7d6abe83cd9501167aa51625c90dd4d31081a631279 |
win32 |
required |
https://github.com/Kitware/CMake/releases/download/v3.16.4/cmake-3.16.4-win64-x64.zip SHA256: f37963bcfcebdfe5864926a3623f6c21220c35790c39cd65e64bd521cbb39c55 |
win64 |
required |
https://github.com/Kitware/CMake/releases/download/v3.16.4/cmake-3.16.4-win64-x64.zip SHA256: f37963bcfcebdfe5864926a3623f6c21220c35790c39cd65e64bd521cbb39c55 |
openocd-esp32¶
OpenOCD for ESP32
License: GPL-2.0-only
More info: https://github.com/espressif/openocd-esp32
Platform |
Required |
Download |
---|---|---|
linux-amd64 |
required |
SHA256: 3460945f3560ef673264a0259a33dcbf0dd18ac6b7b4862e89318655c62215c7 |
linux-arm64 |
required |
SHA256: 65d4de147d37c04e1c65d020e9c38e90db5a71e9e0bc602f5c8e0f44e46cd098 |
linux-armel |
required |
SHA256: 4c03c5fdf73d9a4357cb5e2918c8e3d99900c7a1bb6d50e8712a8d38477398a0 |
linux-armhf |
required |
SHA256: acbb2bf74454ad2e45bab690538082cd6538a687ba2ba3d233309eb985702aba |
macos |
required |
SHA256: 689149120965a8c36c78c1852035b72f500f2a5b406f53624ed4c0a85c4e9a60 |
win32 |
required |
SHA256: 18f5515c4cecce5866e2f7cc7ff536f1a21a624e40a61d24c9dea4a910657cbb |
win64 |
required |
SHA256: 18f5515c4cecce5866e2f7cc7ff536f1a21a624e40a61d24c9dea4a910657cbb |
ninja¶
Ninja build system
On Linux and macOS, it is recommended to install ninja using the OS-specific package manager (like apt, yum, brew, etc.). However, for convenience it is possible to install ninja using idf_tools.py along with the other tools.
License: Apache-2.0
More info: https://github.com/ninja-build/ninja
Platform |
Required |
Download |
---|---|---|
linux-amd64 |
optional |
https://dl.espressif.com/dl/ninja-1.10.0-linux64.tar.gz SHA256: 4b2ad65db438595813b981db921f675f5c775c302b34dc85710ffddf07ec9033 |
macos |
optional |
https://dl.espressif.com/dl/ninja-1.10.0-osx.tar.gz SHA256: 6cd22e2c5fc654282d26b485d9b3d68e242b09a22c2e73a253f2a4a7cfd6774c |
win64 |
required |
https://dl.espressif.com/dl/ninja-1.10.0-win64.zip SHA256: 919fd158c16bf135e8a850bb4046ec1ce28a7439ee08b977cd0b7f6b3463d178 |
idf-exe¶
IDF wrapper tool for Windows
License: Apache-2.0
More info: tools/windows/idf_exe
Platform |
Required |
Download |
---|---|---|
win32 |
required |
https://dl.espressif.com/dl/idf-exe-v1.0.1.zip SHA256: 53eb6aaaf034cc7ed1a97d5c577afa0f99815b7793905e9408e74012d357d04a |
win64 |
required |
https://dl.espressif.com/dl/idf-exe-v1.0.1.zip SHA256: 53eb6aaaf034cc7ed1a97d5c577afa0f99815b7793905e9408e74012d357d04a |
ccache¶
Ccache (compiler cache)
License: GPL-3.0-or-later
More info: https://github.com/ccache/ccache
Platform |
Required |
Download |
---|---|---|
win64 |
required |
https://dl.espressif.com/dl/ccache-3.7-w64.zip SHA256: 37e833f3f354f1145503533e776c1bd44ec2e77ff8a2476a1d2039b0b10c78d6 |
dfu-util¶
dfu-util (Device Firmware Upgrade Utilities)
License: GPL-2.0-only
More info: http://dfu-util.sourceforge.net/
Platform |
Required |
Download |
---|---|---|
win64 |
required |
https://dl.espressif.com/dl/dfu-util-0.9-win64.zip SHA256: 5816d7ec68ef3ac07b5ac9fb9837c57d2efe45b6a80a2f2bbe6b40b1c15c470e |