Nessuna descrizione

Alex Henrie 5ed53c272b Change default PoP argument of esp_prov.get_security from None to string 4 anni fa
.github 83ccca7a19 ci: Use GitHub Actions to generate recursive source code zips for releases 4 anni fa
.gitlab bdaeeb3169 ieee802154: add IEEE 802.15.4 component 4 anni fa
components f29d873c54 Merge branch 'feature/linenoise_improvement' into 'master' 4 anni fa
docs f29d873c54 Merge branch 'feature/linenoise_improvement' into 'master' 4 anni fa
examples f29d873c54 Merge branch 'feature/linenoise_improvement' into 'master' 4 anni fa
make ee2f8b1a62 build system: always build with -fno-jump-tables & -fno-tree-switch-conversion 4 anni fa
mocks 79b0256d63 [driver]: partial mocking of driver component 4 anni fa
tools 5ed53c272b Change default PoP argument of esp_prov.get_security from None to string 4 anni fa
.editorconfig f0ea7a505b style(editorconfig): add indent style for yaml 5 anni fa
.flake8 12152c6272 OpenThread: exclude OpenThread submodule from python style check 4 anni fa
.gitignore 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 anni fa
.gitlab-ci.yml 2800f36416 ci: move target-test unrelated build jobs into host_test stage 4 anni fa
.gitmodules bdaeeb3169 ieee802154: add IEEE 802.15.4 component 4 anni fa
.mypy.ini a22597a2d6 Add mypy check to pre-commit-config 4 anni fa
.pre-commit-config.yaml 7f2973f702 ci: put file sorter to the end of the pre-commit checking 4 anni fa
.pylintrc e326009515 tools: pylint: disable warnings on argument mismatch in ttfw 4 anni fa
.readthedocs.yml 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 anni fa
CMakeLists.txt ee2f8b1a62 build system: always build with -fno-jump-tables & -fno-tree-switch-conversion 4 anni fa
CONTRIBUTING.rst e8dc27add2 add contributing docs 5 anni fa
Kconfig 75bd02bd46 esp32h2: add some more fixes and TODOs 4 anni fa
LICENSE bd6ea4393c Initial public version 9 anni fa
README.md 1c0b26e7fd docs: Linking to a page that helps navigate to documentation for specific ESP32-x chip 4 anni fa
README_CN.md 2b9beaac64 Changed the format of the hyperlink for docs. Merges https://github.com/espressif/esp-idf/pull/7170. 4 anni fa
SUPPORT_POLICY.md 407053592e Drop support for unsupported Python versions 4 anni fa
SUPPORT_POLICY_CN.md 540e5774d9 doc: Update support period policy document 5 anni fa
add_path.sh 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 anni fa
export.bat 6979433dbd Human-readable error if Git or Python are missing. 4 anni fa
export.fish fb70ea6d13 Fixed test autocompletion 4 anni fa
export.ps1 d23989aee2 win_installer: add PowerShell shortcut 5 anni fa
export.sh 38c148b904 Temporarily set LANG to en code to avoid RuntimeError 4 anni fa
install.bat 6979433dbd Human-readable error if Git or Python are missing. 4 anni fa
install.fish f5f0648608 tools: install.fish: Modify method to get base directory. 4 anni fa
install.ps1 bc42073a8b fixes for powershell on unix 5 anni fa
install.sh 47f67f8b81 tools: Prefer python3 during install and export 4 anni fa
requirements.txt 0102cbf334 tools: Add various fixes for idf.py gdbgui 4 anni fa
sdkconfig.rename 66fb5a29bb Whitespace: Automated whitespace fixes (large commit) 5 anni fa

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.