No Description

Ivan Grokhotkov 07a62c2a7d version: Update version to v4.0.4 4 years ago
.github 15f34b4cc2 ci: Use GitHub Actions to generate recursive source code zips for releases 4 years ago
.gitlab 57a9782f8b add simplified CODEOWNERS file for older release branches 4 years ago
components 566231f33b version: Update version to v4.0.4 4 years ago
docs 756beb0e7a Merge branch 'test/merge_ble_mesh_node_and_provioner_in_console_v4.0' into 'release/v4.0' 4 years ago
examples bd6fadce2b Merge branch 'fix/update_https_example_root_certificate_v4.0' into 'release/v4.0' 4 years ago
make 566231f33b version: Update version to v4.0.4 4 years ago
tools 566231f33b version: Update version to v4.0.4 4 years ago
.editorconfig 88df8fd293 cmake: Use cmake_lint project, tidy up all CMake source files 7 years ago
.flake8 b75f8b1b20 ESP Local Control Feature Added 6 years ago
.gitignore 04d24c750a tools: new installer for Windows 6 years ago
.gitlab-ci.yml aa6b080002 ci: Add retries on runner system failures 4 years ago
.gitmodules c9cf0afb6e tools: Add a script for switching to real submodules in forks 6 years ago
.readthedocs.yml 363f3e8311 docs: Remove building of zipped HTML docs from build process and consequently from Downloads as many users don't use that. We are still providing PDF documentation for people who prefer viewing docs off-line. Removal of this build step is expected to save almost 10 minutes of build time and resolve issue of build failures because of hitting 40 min build time limit on Read The Docs. 6 years ago
.travis.yml 9273de8b43 Check the Python coding style 7 years ago
CMakeLists.txt 3ba480ba53 cmake: error out on building in IDF_PATH root dir 5 years ago
CONTRIBUTING.rst ed0db52f74 docs: This is a quick reference of more than a dozen and-ons and extensions prepared over the last two years to add contents, improve look & feel and cut on maintenance of the ESP-IDF documentation. 7 years ago
Kconfig 2a4173e9a6 Docs: Encourage to used Python 3 5 years ago
LICENSE bd6ea4393c Initial public version 9 years ago
README.md 87e56f132b docs: remove the read the docs CI badge 4 years ago
SUPPORT_POLICY.md 5e505898df docs: Add ESP-IDF support period policy 6 years ago
add_path.sh 12b6da0388 tools: {install,export}.{bat,sh} tools 6 years ago
export.bat d2b0cfc7e4 Human-readable error if Git or Python are missing. 4 years ago
export.sh b086a41569 tools: Prefer python3 during install and export 4 years ago
install.bat d2b0cfc7e4 Human-readable error if Git or Python are missing. 4 years ago
install.sh b086a41569 tools: Prefer python3 during install and export 4 years ago
requirements.txt 20156f9702 idf.py: Add support for action specific options 6 years ago
sdkconfig.rename c5000c83d2 Rename Kconfig options (root) 6 years ago

README.md

Espressif IoT Development Framework

ESP-IDF is the official development framework for the ESP32 chip provided for Windows, Linux and macOS.

Developing With ESP-IDF

Setting Up ESP-IDF

See setup guides for detailed instructions to set up the ESP-IDF:

Non-GitHub forks

ESP-IDF uses relative locations as its submodules URLs (.gitmodules). So they link to GitHub. If ESP-IDF is forked to a Git repository which is not on GitHub, you will need to run the script tools/set-submodules-to-github.sh after git clone. The script sets absolute URLs for all submodules, allowing git submodule update --init --recursive to complete. If cloning ESP-IDF from GitHub, this step is not needed.

Finding a Project

As well as the esp-idf-template project mentioned in Getting Started, ESP-IDF comes with some example projects in the examples directory.

Once you've found the project you want to work with, change to its directory and you can configure and build it.

To start your own project based on an example, copy the example project directory outside of the ESP-IDF directory.

Quick Reference

See the Getting Started guide links above for a detailed setup guide. This is a quick reference for common commands when working with ESP-IDF projects:

Setup Build Environment

(See the Getting Started guide listed above for a full list of required steps with more details.)

  • Install host build dependencies mentioned in the Getting Started guide.
  • Run the install script to set up the build environment. The options include install.bat for Windows, and install.sh for Unix shells.
  • Run the export script on Windows (export.bat) or source it on Unix (source export.sh) in every shell environment before using ESP-IDF.

Configuring the Project

idf.py menuconfig opens a text-based configuration menu where you can configure the project.

Compiling the Project

idf.py build

... will compile app, bootloader and generate a partition table based on the config.

Flashing the Project

When the build finishes, it will print a command line to use esptool.py to flash the chip. However you can also do this automatically by running:

idf.py -p PORT flash

Replace PORT with the name of your serial port (like COM3 on Windows, /dev/ttyUSB0 on Linux, or /dev/cu.usbserial-X on MacOS. If the -p option is left out, idf.py flash will try to flash the first available serial port.

This will flash the entire project (app, bootloader and partition table) to a new chip. The settings for serial port flashing can be configured with idf.py menuconfig.

You don't need to run idf.py build before running idf.py flash, idf.py flash will automatically rebuild anything which needs it.

Viewing Serial Output

The idf.py monitor target uses the idf_monitor tool to display serial output from the ESP32. idf_monitor also has a range of features to decode crash output and interact with the device. Check the documentation page for details.

Exit the monitor by typing Ctrl-].

To build, flash and monitor output in one pass, you can run:

idf.py flash monitor

Compiling & Flashing Only the App

After the initial flash, you may just want to build and flash just your app, not the bootloader and partition table:

  • idf.py app - build just the app.
  • idf.py app-flash - flash just the app.

idf.py app-flash will automatically rebuild the app if any source files have changed.

(In normal development there's no downside to reflashing the bootloader and partition table each time, if they haven't changed.)

Erasing Flash

The idf.py flash target does not erase the entire flash contents. However it is sometimes useful to set the device back to a totally erased state, particularly when making partition table changes or OTA app updates. To erase the entire flash, run idf.py erase_flash.

This can be combined with other targets, ie idf.py -p PORT erase_flash flash will erase everything and then re-flash the new app, bootloader and partition table.

Resources