Nav apraksta

pedro.minatel cccdb3e4aa Get started example update for addressable LED compatibility. 5 gadi atpakaļ
.github 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 gadi atpakaļ
.gitlab 2e3367b97e update api-guides/build-system.rst to keep EN and CN in sync 5 gadi atpakaļ
components 2c0962f727 Merge branch 'feature/spi_flash_auto_suspend_default_on_c3' into 'master' 5 gadi atpakaļ
docs d9c004ad94 Merge branch 'docs/c3-devkitm-1' into 'master' 5 gadi atpakaļ
examples cccdb3e4aa Get started example update for addressable LED compatibility. 5 gadi atpakaļ
make 3587203495 tools: Invoke menuconfig as named module 5 gadi atpakaļ
tools 1289918204 Merge branch 'refactor/ldgen_generation_changes' into 'master' 5 gadi atpakaļ
.editorconfig 7951152f7b CI: Refactor CI rules into `rules.yml`. 5 gadi atpakaļ
.flake8 54ae6b871d Add Python-style ignore for the cmock component 5 gadi atpakaļ
.gitignore 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 gadi atpakaļ
.gitlab-ci.yml 88aa3c2463 docs: bump cairosvg from 2.4.2 to 2.5.1 in /docs 5 gadi atpakaļ
.gitmodules 20c068ef3b cmock: added cmock as component 5 gadi atpakaļ
.pre-commit-config.yaml a4f2206d4c pre-commit: Add double-quote-string-fixer and isort for python files 5 gadi atpakaļ
.pylintrc 26e1e5ece8 pylint: increase instance attribute number from 7 to 12 5 gadi atpakaļ
.readthedocs.yml 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 gadi atpakaļ
CMakeLists.txt ed7fbfefac build system: don't add GCC-specific options when building with clang 5 gadi atpakaļ
CONTRIBUTING.rst e8dc27add2 add contributing docs 5 gadi atpakaļ
Kconfig fa7aa656d3 build-system: add loadable elf support for ESP32-S2 and C3 5 gadi atpakaļ
LICENSE bd6ea4393c Initial public version 9 gadi atpakaļ
README.md 23eadafd38 Fix the setup instructions in the main README 5 gadi atpakaļ
README_CN.md 71d1b32dde docs: Provide link to ESP32-S2 specific documentation 5 gadi atpakaļ
SUPPORT_POLICY.md 7a9abe3ec5 add chart of version support to version.rst 5 gadi atpakaļ
SUPPORT_POLICY_CN.md 540e5774d9 doc: Update support period policy document 5 gadi atpakaļ
add_path.sh 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 gadi atpakaļ
export.bat 12b6da0388 tools: {install,export}.{bat,sh} tools 6 gadi atpakaļ
export.fish 346b002d9a enable autocompletion for command idf.py 5 gadi atpakaļ
export.ps1 d23989aee2 win_installer: add PowerShell shortcut 5 gadi atpakaļ
export.sh 304cff9f75 Redirect warning to stderr and unset temporary shell procedure 5 gadi atpakaļ
install.bat f38c1c18a8 tools: install.bat: bail out if idf_tools.py call fails 6 gadi atpakaļ
install.fish 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 gadi atpakaļ
install.ps1 bc42073a8b fixes for powershell on unix 5 gadi atpakaļ
install.sh 12b6da0388 tools: {install,export}.{bat,sh} tools 6 gadi atpakaļ
requirements.txt 4e8497dda6 core dump: add extra pip dependency construct==2.10.54 5 gadi atpakaļ
sdkconfig.rename 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 gadi atpakaļ

README.md

Espressif IoT Development Framework

ESP-IDF is the official development framework for the ESP32 and ESP32-S Series SoCs 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:

Chip Getting Started Guides for ESP-IDF
ESP32
ESP32-S2

Note: Each ESP-IDF release has its own documentation. Please see Section Versions 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 ESP32 or ESP32-S Series 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