ESP-IDF Extension for VS Code

中文

Develop, build, flash, monitor, debug and more with Espressif chips using Espressif IoT Development Framework (ESP-IDF).

Latest master installer for Visual Studio Code. You can use this VSIX to test the current github master of the extension by pressing F1 or click menu View -> Command Palette..., type Install from VSIX and then select the previously downloaded .vsix file to install the extension.

Make sure to review our Espressif documentation first to properly use the extension.

How to use

Install

1. Download and install Visual Studio Code.

2. Install ESP-IDF system prerequisites for your operating system:

• Prerequisites for MacOS and Linux.
• For Windows there is no additional prerequisites.

3. In Visual Studio Code, Open the Extensions view by clicking on the Extension icon in the Activity Bar on the side of Visual Studio Code or the View: Show Extensions command (shortcut: ⇧ ⌘ X or Ctrl+Shift+X).

4. Search for ESP-IDF Extension.

5. Install the extension. After you install the extension, the should appear in the VS Code Activity bar (left side set of icons). When you click the Espressif icon, you can see a list of basic commands provided by this extension.

6. From the command list, select Configure ESP-IDF Extension or press F1 and type Configure ESP-IDF Extension. After, choose the ESP-IDF: Configure ESP-IDF Extension option.

   NOTE: For versions of ESP-IDF < 5.0, spaces are not supported inside configured paths.

7. Choose Express and select the download server:

• Espressif: Faster speed in China using Espressif download servers links.
• Github: Using github releases links.

8. Pick an ESP-IDF version to download or the Find ESP-IDF in your system option to search for existing ESP-IDF directory.

9. Choose the location for ESP-IDF Tools (also known as IDF_TOOLS_PATH) which is $HOME\.espressif on MacOS/Linux and %USERPROFILE%\.espressif on Windows by default.

10. If your operating system is MacOS/Linux, choose the system Python executable to create ESP-IDF virtual environment inside ESP-IDF Tools and install ESP-IDF Python package there.

    NOTE: Windows users don't need to select a Python executable since it is going to be installed by this setup.

11. Make sure that IDF_TOOLS_PATH doesn't have any spaces to avoid any build issues. Also make sure that IDF_TOOLS_PATH is not the same directory as IDF_PATH.

12. You will see a page showing the setup progress status, including ESP-IDF download progress, ESP-IDF Tools download and install progress as well as the creation of a Python virtual environment.

13. If everything is installed correctly, you will see a message that all settings have been configured. You can start using the extension.

Check the Troubleshooting section if you have any issues.

Using the ESP-IDF Extension for VS Code

This extension provides a list of icons in the status bar (blue bar in the bottom of VS Code window) for ESP-IDF commands. You can see the command to be executed when you hover the icon.

These icons will be used in the steps below showing common ESP-IDF use cases:

1. Press F1 and type ESP-IDF: Show Examples Projects to create a new project from ESP-IDF examples. Select ESP-IDF and choose an example to create a new project from.

2. Once the project is created and opened in VS Code, set the serial port of your device by clicking status bar icon . Alternatively, press F1, type ESP-IDF: Select Port to Use, and choose the serial port to which your device is connected.

3. Select an Espressif target (esp32, esp32s2, etc.) by clicking status bar icon . Alternatively, press F1 and type ESP-IDF: Set Espressif Device Target command.

4. Next, configure your ESP-IDF project by clicking status bar icon or press F1 and typing ESP-IDF: SDK Configuration Editor command (CTRL E G keyboard shortcut) where you can modify the ESP-IDF project settings. After all changes are made, click Save and close this window. You can see the output in the menu View -> Output and choose ESP-IDF from the dropdown list.

5. (OPTIONAL) Run ESP-IDF: Run idf.py reconfigure Task to generate the compile_commands.json file so language support works. Additionally you can configure the .vscode/c_cpp_properties.json as explained in C/C++ Configuration documentation.

6. At this point, you can modify the code. When the project is completed, build your project by clicking status bar icon or pressing F1 and typing ESP-IDF: Build your Project.

7. Flash to your device by clicking status bar icon , or pressing F1 and typing ESP-IDF: Flash Your Project. From there, select UART, DFU or JTAG depending on your serial connection, and start flashing the application to your device.

8. Change the flash method by clicking status bar icon , or pressing F1 and typing ESP-IDF: Select Flash Method to select from UART, DFU or JTAG. You can alternatively use one of the commands ESP-IDF: Flash (UART) Your Project, ESP-IDF: Flash (with JTAG) or ESP-IDF: Flash (DFU) Your Project.

9. Start a monitor by clicking status bar icon , or pressing F1 and typing ESP-IDF: Monitor Device, which will log the device activity in a Visual Studio Code terminal.

10. Make sure to configure your drivers as mentioned in ESP-IDF Configure JTAG Interface documentation.

11. Before debugging your device, select the device OpenOCD board configuration files by pressing F1 and typing ESP-IDF: Select OpenOCD Board Configuration. You can test the connection by clicking status bar icon or pressing F1 and typing ESP-IDF: OpenOCD Manager. The output is shown in the menu View -> Output and choose ESP-IDF from the dropdown list.

    NOTE: You can start or stop the OpenOCD in Visual Studio Code using the ESP-IDF: OpenOCD Manager command or by clicking the OpenOCD Server (Running | Stopped) button in the status bar.

12. If you want to start a debug session, just press F5 (ensure the project is built, flashed, and OpenOCD is properly connected for the debugger to function correctly). The debug session output can be seen in the menu View -> Debug Console.

Check the Troubleshooting section if you have any issues.

Further reading

Check the ESP-IDF Extension for VS Code Documentation for tutorials, commands and features provided.

All Available Commands

Press F1 or click menu View -> Command Palette... to show Visual Studio code commands, then type ESP-IDF to see all available extension commands.

Category	Command	Description	Keyboard Shortcuts (Mac)	Keyboard Shortcuts (Windows/Linux)
Settings	Add Docker Container Configuration	Add the .devcontainer files to the currently opened project directory, necessary to use a ESP-IDF project in a Docker container with Visual Studio Code Dev Containers extension.
	Add VS Code Configuration Folder	Add .vscode files to the currently opened project directory. This includes launch.json (for debugging), settings.json and c_cpp_properties.json (for syntax highlight).
	Configure ESP-IDF Extension	Open a window with a setup wizard to install ESP-IDF, IDF Tools and Python virtual environment.
	Select Output and Notification Mode	This extension shows many notifications and output in the Output window ESP-IDF. This command allows you to set if to show notifications only, output only, both notifications and output, or neither.
	Select Where to Save Configuration Settings	In Visual Studio Code, settings can be saved in 3 places: User Settings (global settings), workspace ( .code-workspace file) or workspace folder (.vscode/settings.json). More information in working with multiple projects.
	Pick a Workspace Folder	When using a Visual Studio Code workspace with multiple folders, this command allows you to choose which workspace folder to apply this extension’s commands to. More information in working with multiple projects.
Basic	Show Examples Projects	Launch UI to show examples from selected framework and allow you to create a project from them. This command will show frameworks already configured in the extension, so to view ESP-Rainmaker examples, you need to run the Install ESP-Rainmaker first (or set the equivalent setting idf.espRainmakerPath), and then execute this command to see the examples.
	Set Espressif Device Target	This will set the target for the current project (IDF_TARGET). Similar to idf.py set-target. For example, if you want to use ESP32 or ESP32-C3, you need to execute this command.
	SDK Configuration Editor	Launch a UI to configure your ESP-IDF project settings. This is equivalent to idf.py menuconfig.	⌘ I G	Ctrl E G
	Build Your Project	Build your project using `CMake` and `Ninja-build` as explained in ESP-IDF Build System Using Cmake Directly. You could modify the behavior of the build task with idf.cmakeCompilerArgs for Cmake configure step and idf.ninjaArgs for Ninja step. For example, using [-j N] where N is the number of jobs run in parallel.	⌘ I B	Ctrl E B
	Size Analysis of the Binaries	Launch UI with the ESP-IDF project binaries size information.	⌘ I S	Ctrl E S
	Select Port to Use	Select which serial port to use for ESP-IDF tasks, such as flashing or monitoring your device.	⌘ I P	Ctrl E P
	Flash Your Project	Write binary data to the ESP’s flash chip from your current ESP-IDF project. This command will use either UART, DFU or JTAG based on idf.flashType.	⌘ I F	Ctrl E F
	Monitor Device	This command will execute idf.py monitor to start serial communication with Espressif device. Please take a look at the IDF Monitor.	⌘ I M	Ctrl E M
	Open ESP-IDF Terminal	Launch a terminal window configured with extension ESP-IDF settings. Similar to export.sh script from ESP-IDF CLI.	⌘ I T	Ctrl E T
	Select OpenOCD Board Configuration	Select the OpenOCD configuration files that match your Espressif device target, such as DevKitC or ESP-Wrover-Kit. This is necessary for flashing with JTAG or debugging your device.
	Build, Flash and Start a Monitor on Your Device	Build the project, write binaries program to device and start a monitor terminal with a single command. Similar to idf.py build flash monitor.	⌘ I D	Ctrl E D
Project creation	Show Examples Projects	Launch UI to show examples from selected framework and allow you to create a project from them. This command will show frameworks already configured in the extension, so to view ESP-Rainmaker examples, you need to run the Install ESP-Rainmaker first (or set the equivalent setting idf.espRainmakerPath), and then execute this command to see the examples.
	Create Project from Extension Template	Create an ESP-IDF project using one of the extension template projects.	⌘ I C	Ctrl E C
	Create New ESP-IDF Component	Create a new component in the current directory based on ESP-IDF component template.
	Import ESP-IDF Project	Import an existing ESP-IDF project, add .vscode and .devcontainer files to a new location, and optionally rename the project.
	New Project	Launch UI with a ESP-IDF project creation wizard using example templates from ESP-IDF and additional frameworks configured in the extension.	⌘ I N	Ctrl E N
Flashing	Select Flash Method	Select which flash method to use for Flash your project command. It can be DFU, JTAG or UART.
	Flash Your Project	Write binary data to the ESP’s flash chip from your current ESP-IDF project. This command will use either UART, DFU or JTAG based on idf.flashType	⌘ I F	Ctrl E F
	Flash (DFU) Your Project	Write binary data to the ESP’s flash chip from your current ESP-IDF project using DFU. Only for ESP32-S2 and ESP32-S3.
	Flash (UART) Your Project	Write binary data to the ESP’s flash chip from your current ESP-IDF project using esptool.py.
	Flash (with JTAG)	Write binary data to the ESP’s flash chip from your current ESP-IDF project using OpenOCD JTAG.
	Encrypt and Flash Your Project	Execute flashing the project program to device while adding --encrypt for partitions to be encrypted.
	Erase Flash Memory from Device	Execute esptool.py erase_flash command to erase flash chip (set to 0xFF bytes).	⌘ I R	Ctrl E R
Code coverage	Add Editor Coverage	Parse your project GCOV code coverage files to add color lines representing code coverage on currently opened source code file.
	Configure Project SDKConfig for Coverage	Set required values in your project SDKConfig to enable code coverage analysis.
	Get HTML Coverage Report for Project	Parse your project GCOV code coverage files to generate a HTML coverage report.
	Remove Editor Coverage	Remove editor colored lines from Add Editor coverage command
Additional frameworks	Install ESP-ADF	Clone ESP-ADF inside the selected directory and set idf.espAdfPath (idf.espAdfPathWin in Windows) configuration setting.
	Add Arduino ESP32 as ESP-IDF Component	Add Arduino-ESP32 as a ESP-IDF component in your current directory (${CURRENT_DIRECTORY}/components/arduino).
	Install ESP-IDF Python Packages (DEPRECATION NOTICE)	Install extension Python packages. This command is deprecated and will be removed soon.
	Install ESP-MDF	Clone ESP-MDF inside the selected directory and set idf.espMdfPath (idf.espMdfPathWin in Windows) configuration setting.
	Install ESP-Matter	Clone ESP-Matter and set idf.espMatterPath. ESP-Matter is not supported in Windows. Make sure to install Matter system prerequisites first.
	Set ESP-MATTER Device Path (ESP_MATTER_DEVICE_PATH)	The ESP-IDF: Set ESP-MATTER Device Path (ESP_MATTER_DEVICE_PATH) is used to define the device path for ESP-Matter. ESP-Matter is not supported in Windows.
	Install ESP-Rainmaker	Clone ESP-Rainmaker and set idf.espRainmakerPath (idf.espRainmakerPathWin in Windows) configuration setting.
	Install ESP-HomeKit-SDK	Clone ESP-HomeKit-SDK inside the selected directory and set idf.espHomeKitSdkPath (idf.espHomeKitSdkPathWin in Windows) configuration setting.
eFuse	Get eFuse Summary	Retrieve a list of eFuses and their corresponding values from the chip currently connected to the serial port.
	Clear eFuse Summary	Clear the eFuse Summary tree from ESP Explorer EFUSEEXPLORER.
QEMU	Launch QEMU Server	As described in QEMU documentation, this command will execute ESP32 QEMU from the project Dockerfile with the current project binaries.
	Launch QEMU Debug Session	As described in QEMU documentation, this command will start a debug session to ESP32 QEMU from the project Dockerfile with the current project binaries.
	Monitor QEMU Device	As described in QEMU documentation, this command will start a terminal to monitor the ESP32 QEMU from the project Dockerfile with the current project binaries.
Monitoring	Monitor Device	This command will execute idf.py monitor to start serial communication with Espressif device. Please take a look at the IDF Monitor Documentation.	⌘ I M	Ctrl E M
	Launch IDF Monitor for Core Dump Mode/GDB Stub Mode	Launch ESP-IDF Monitor with WebSocket capabilities. If you has configured the panic handler to gdbstub or core dump, the monitor will launch a post-mortem debug session of the chip.
	Monitor QEMU Device	As described in QEMU documentation, this command will start a terminal to monitor the ESP32 QEMU from the project Dockerfile with the current project binaries.
Editors	NVS Partition Editor	Launch UI to create a CSV file for ESP-IDF Non-Volatile Storage Library.
	Partition Table Editor	Launch UI to manage custom partition table as described in ESP-IDF Partition Tables.
	SDK Configuration Editor	Launch a UI to configure your ESP-IDF project settings. This is equivalent to idf.py menuconfig.	⌘ I G	Ctrl E G
Unit Testing	Unit Test: Build and Flash Unit Test App for Testing	Copy the unit test app in the current project, build the current project and flash the unit test application to the connected device. More information in Unit testing documentation.
	Unit Test: Install ESP-IDF PyTest Requirements	Install the ESP-IDF Pytest requirements packages to be able to execute ESP-IDF Unit tests. More information in Unit testing documentation.
Scripts and Tools	Run idf.py reconfigure Task	This command will execute idf.py reconfigure (CMake configure task), which is useful for generating compile_commands.json for the C/C++ language support.
	Erase Flash Memory from Device	Execute esptool.py erase_flash command to erase flash chip (set to 0xFF bytes).	⌘ I R	Ctrl E R
	Dispose of Current SDK Configuration Editor Server Process	If you already executed the SDK Configuration Editor, a cache process will remain in the background for faster reopening. This command will dispose of such cache process.
	Doctor Command	Run a diagnostic of the extension setup settings and extension logs to provide a troubleshooting report.
	Troubleshoot Form	Launch UI for user to send a troubleshoot report with steps to reproduce. Run a diagnostic of the extension setup settings and extension logs to send to telemetry backend.
	Run ESP-IDF-SBOM Vulnerability Check	Creates Software bill of materials (SBOM) files in the Software Package Data Exchange (SPDX) format for applications generated by the Espressif IoT Development Framework (ESP-IDF).
	Save Default SDKCONFIG File (save-defconfig)	Generate sdkconfig.defaults files using the project current sdkconfig file.
	Show Ninja Build Summary	Execute the Chromium ninja-build-summary.py.
	Search in documentation...	Select some text from your source code file and search in ESP-IDF documentation with results right in the VS Code ESP-IDF Explorer tab.	⌘ I Q	Ctrl E Q
	Search Error Hint	Type some text to find a matching error from ESP-IDF hints dictionary.
Cleanup	Clear ESP-IDF Search Results	Clear results from ESP Explorer Documentation Search Results.
	Clear Saved ESP-IDF Setups	Clear existing ESP-IDF setups saved by the extension.

Commands for tasks.json and launch.json

We have implemented some utilities commands that can be used in tasks.json and launch.json like:

"miDebuggerPath": "${command:espIdf.getToolchainGdb}"

• espIdf.getExtensionPath: Get the installed location absolute path.
• espIdf.getOpenOcdScriptValue: Return the value of OPENOCD_SCRIPTS computed from ESP-IDF Tools path, idf.customExtraVars, or the system's OPENOCD_SCRIPTS environment variable.
• espIdf.getOpenOcdConfig: Return the openOCD configuration files as string. Example -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp32-wrover.cfg.
• espIdf.getProjectName: Return the project name from current workspace folder build/project_description.json.
• espIdf.getToolchainGcc: Return the absolute path of the toolchain GCC for the ESP-IDF target given by current IDF_TARGET in sdkconfig.
• espIdf.getToolchainGdb: Return the absolute path of the toolchain gdb for the ESP-IDF target given by current IDF_TARGET in sdkconfig.

See an example in the debugging documentation.

Available Tasks in tasks.json

A template tasks.json is included when creating a project using ESP-IDF: Create Project from Extension Template. These tasks can be executed by pressing F1, writing Tasks: Run task and selecting one of the following:

1. Build - Build Project
2. Set Target to esp32
3. Set Target to esp32s2
4. Clean - Clean the project
5. Flash - Flash the device
6. Monitor - Start a monitor terminal
7. OpenOCD - Start the OpenOCD server
8. BuildFlash - Execute a build followed by a flash command

Note that for OpenOCD tasks, you need to define OpenOCD_SCRIPTS in your system environment variables with OpenOCD scripts folder path.

Troubleshooting

If something is not working, please check for any error on one of these:

NOTE: Use idf.OpenOCDDebugLevel configuration setting to 3 or more to show debug logging in OpenOCD server output.

NOTE: Use logLevel in your /.vscode/launch.json to 3 or more to show more debug adapter output.

1. In Visual Studio Code select menu View > Output > ESP-IDF. This output information is useful to know what is happening in the extension.
2. In Visual Studio Code select menu View > Command Palette... and type ESP-IDF: Doctor Command to generate a report of your environment configuration and it will be copied in your clipboard to paste anywhere.
3. Check log file which can be obtained from:

• Windows: %USERPROFILE%\.vscode\extensions\espressif.esp-idf-extension-VERSION\esp_idf_vsc_ext.log
• Linux & MacOSX: $HOME/.vscode/extensions/espressif.esp-idf-extension-VERSION/esp_idf_vsc_ext.log

4. In Visual Studio Code, select menu Help > Toggle Developer Tools and copy any error in the Console tab related to this extension.

5. Visual Studio Code allows you to configure settings at different levels: Global (User Settings), Workspace and Workspace Folder, so make sure your project has the right settings. The ESP-IDF: Doctor command result might give the values from user settings instead of the workspace folder settings.

6. Refer to the OpenOCD troubleshooting FAQ for help with application tracing, debugging, or other OpenOCD-related issues that may appear in the OpenOCD output.

7. In some cases, the default shell (Powershell, zsh, sh, .etc) configured in VS Code could affect the behavior of the extension. Make sure that MSYS/MinGW is not set in the environment and the variables don't conflict with terminal behavior. The ESP-IDF: Doctor Command shows which shell is detected by the extension when running tasks like building, flashing and monitoring. More information in here.

If there is any Python package error, please try to reinstall the required Python packages with the ESP-IDF: Install ESP-IDF Python Packages command or running the setup again with the ESP-IDF: Configure ESP-IDF Extension command.

NOTE: When downloading ESP-IDF using git cloning in Windows, if you receive errors like "unable to create symlink", enabling Developer Mode while cloning ESP-IDF could help resolve the issue.

If you can't resolve the error, please search in the github repository issues for existing errors or open a new issue here.

Code of Conduct

This project and everyone participating in it is governed by the Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].

License

This extension is licensed under the Apache License 2.0. Please see the LICENSE file for additional copyright notices and terms.