暂无描述

Ivan Grokhotkov 1995644298 versions: Update version to 4.3.2 4 年之前
.github 6121046090 ci: Use GitHub Actions to generate recursive source code zips for releases 4 年之前
.gitlab 0261b78c0c gitlab: simplify approvals for backports (v4.3) 4 年之前
components 8bf14a9238 versions: Update version to 4.3.2 4 年之前
docs 55e415377d Merge branch 'docs/update_the_assignment_type_in_i2s_programming_example' into 'release/v4.3' 4 年之前
examples 233dc30fb1 Merge branch 'bugfix/pppos_event_deinit_exit_ppp_v4.3' into 'release/v4.3' 4 年之前
make 8bf14a9238 versions: Update version to 4.3.2 4 年之前
tools 8bf14a9238 versions: Update version to 4.3.2 4 年之前
.editorconfig 7951152f7b CI: Refactor CI rules into `rules.yml`. 5 年之前
.flake8 54ae6b871d Add Python-style ignore for the cmock component 5 年之前
.gitignore 29accf2533 soc/ll: workaround compiler bug that generate 8/16 bits inst instead of 32 bits one 4 年之前
.gitlab-ci.yml d85b0b869b ci: Add retries on runner system failures 4 年之前
.gitmodules cdcb85fd70 component/bt: add another bt-lib submodule and refactor the directories 4 年之前
.pre-commit-config.yaml a4f2206d4c pre-commit: Add double-quote-string-fixer and isort for python files 5 年之前
.pylintrc 26e1e5ece8 pylint: increase instance attribute number from 7 to 12 5 年之前
.readthedocs.yml 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 年之前
CMakeLists.txt a6371d2a97 [nvs] nvs page host runs in CI, fix build failure 4 年之前
CONTRIBUTING.rst e8dc27add2 add contributing docs 5 年之前
Kconfig 84e4127f0c tests: gdb_loadable_elf: adjust the breakpoint location for ESP32 ECO3 4 年之前
LICENSE bd6ea4393c Initial public version 9 年之前
README.md 186fcc328b docs: Linking to a page that helps navigate to documentation for specific ESP32-x chip 4 年之前
README_CN.md 186fcc328b docs: Linking to a page that helps navigate to documentation for specific ESP32-x chip 4 年之前
SUPPORT_POLICY.md 7a9abe3ec5 add chart of version support to version.rst 5 年之前
SUPPORT_POLICY_CN.md 540e5774d9 doc: Update support period policy document 5 年之前
add_path.sh 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 年之前
export.bat 7092d7eff5 tools: {install, export}.bat: fix path quoting 4 年之前
export.fish e66fec955e Fixed test autocompletion 4 年之前
export.ps1 896f6f2dfc Tools: Make clear the used platform in the PowerShell export script 4 年之前
export.sh beba6f954c Temporarily set LANG to en code to avoid RuntimeError 4 年之前
install.bat 7092d7eff5 tools: {install, export}.bat: fix path quoting 4 年之前
install.fish 0f15c28a84 Fix install.fish 4 年之前
install.ps1 5639b6888d tools: Installing tools for given IDF_TARGET 4 年之前
install.sh 5639b6888d tools: Installing tools for given IDF_TARGET 4 年之前
requirements.txt 2dec9fadf9 Tools: Constrain the cffi package for older pythons 4 年之前
sdkconfig.rename 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 年之前

README.md

Espressif IoT Development Framework

ESP-IDF is the development framework for Espressif SoCs (released after 20161) provided for Windows, Linux and macOS.

Developing With ESP-IDF

Setting Up ESP-IDF

See https://idf.espressif.com/ for links to detailed instructions on how to set up the ESP-IDF depending on chip you use.

Note: Each SoC series and each ESP-IDF release has its own documentation. Please see Section Versions on how to find documentation and how to checkout specific release of 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 or install.ps1 for Windows, and install.sh or install.fish 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 set-target <chip_name> sets the target of the project to <chip_name>. Run idf.py set-target without any arguments to see a list of supported targets.
  • 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 Espressif SoCs. 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


1: ESP8266 and ESP8285 are not supported in ESP-IDF. See RTOS SDK instead.