Fără Descriere

Ivan Grokhotkov cfdfeed973 freertos: linker.lf rules fixes 5 ani în urmă
.github 83ccca7a19 ci: Use GitHub Actions to generate recursive source code zips for releases 4 ani în urmă
.gitlab 691e30e659 advanced_https_ota: Add example test for OTA with OpenSSL server with binary file aligned to 289 byte boundary 4 ani în urmă
components cfdfeed973 freertos: linker.lf rules fixes 4 ani în urmă
docs 58424ccebf Merge branch 'bugfix/doc_jtag_c3' into 'master' 4 ani în urmă
examples f14cdd8a31 Merge branch 'test/esp_ssl_example' into 'master' 4 ani în urmă
make f314e41f67 make build system: Produce an error if BUILD_DIR_BASE is a Windows-style path 4 ani în urmă
tools 823abfdfd5 examples: Add esp-ssl example tests `server/client` 4 ani în urmă
.editorconfig f0ea7a505b style(editorconfig): add indent style for yaml 5 ani în urmă
.flake8 12152c6272 OpenThread: exclude OpenThread submodule from python style check 4 ani în urmă
.gitignore 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 ani în urmă
.gitlab-ci.yml 4429bc83ea ci: update docker image version for docs 4 ani în urmă
.gitmodules 7c38989309 OpenThread: add OpenThread and porting 4 ani în urmă
.mypy.ini a22597a2d6 Add mypy check to pre-commit-config 5 ani în urmă
.pre-commit-config.yaml e408915ff0 Remove sorting of MYPY ignore list from py script 4 ani în urmă
.pylintrc 4d3c2e284e style(pylint): exclude checkers "too many nested_blocks/branches/statements" 5 ani în urmă
.readthedocs.yml 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 ani în urmă
CMakeLists.txt 2fb5b42eb1 [nvs] add nvs page host test to CI 4 ani în urmă
CONTRIBUTING.rst e8dc27add2 add contributing docs 5 ani în urmă
Kconfig 793771e744 Merge branch 'feature/esp_error_check_return' into 'master' 4 ani în urmă
LICENSE bd6ea4393c Initial public version 9 ani în urmă
README.md 5a8a6c8fff docs: Provide new links to documentation for ESP32-S2 and ESP32-C3 chips 5 ani în urmă
README_CN.md 5a8a6c8fff docs: Provide new links to documentation for ESP32-S2 and ESP32-C3 chips 5 ani în urmă
SUPPORT_POLICY.md 16f76976d5 Remove deprecated versions from SUPPORT_POLICY.md 4 ani în urmă
SUPPORT_POLICY_CN.md 540e5774d9 doc: Update support period policy document 5 ani în urmă
add_path.sh 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 ani în urmă
export.bat 6979433dbd Human-readable error if Git or Python are missing. 4 ani în urmă
export.fish 47f67f8b81 tools: Prefer python3 during install and export 5 ani în urmă
export.ps1 d23989aee2 win_installer: add PowerShell shortcut 5 ani în urmă
export.sh 16731833fb add default value for unset env variables 4 ani în urmă
install.bat 6979433dbd Human-readable error if Git or Python are missing. 4 ani în urmă
install.fish f5f0648608 tools: install.fish: Modify method to get base directory. 4 ani în urmă
install.ps1 bc42073a8b fixes for powershell on unix 5 ani în urmă
install.sh 47f67f8b81 tools: Prefer python3 during install and export 5 ani în urmă
requirements.txt b77addea2f Decompose idf_monitor.py 4 ani în urmă
sdkconfig.rename 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 ani în urmă

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
ESP32-C3

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