alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
Espressif IoT Development Framework. Official development framework for Espressif SoCs. https://docs.espressif.com/projects/esp-idf/en/stable/esp32/index.html
27,056 Commits 20 Branches 148 Tags 384 MiB
C 95.6%
Python 2.1%
C++ 1.2%
CMake 0.7%
Assembly 0.3%
f0bea3ce51
Go to file
morris f0bea3ce51 mcpwm: support not reset GPIO config at exit 
By default, the driver will reset the GPIO used by the MCPWM capture
channel at exit. But in some special use cases, the same gpio may also
be used by another device, which shares the same gpio configuration,
resetting the gpio is not expected.

Closes https://github.com/espressif/esp-idf/issues/10327
2022-12-12 17:50:06 +08:00
.github Merge branch 'contrib/github_pr_9273' into 'master' 2022-09-12 17:46:14 +08:00
.gitlab Merge branch 'feature/linux_esp_hw_support' into 'master' 2022-12-12 09:59:31 +08:00
components mcpwm: support not reset GPIO config at exit 2022-12-12 17:50:06 +08:00
docs Merge branch 'docs/freertos_smp_critical_section_usage' into 'master' 2022-12-10 02:08:30 +08:00
examples Merge branch 'bugfix/system_examples_print_format' into 'master' 2022-12-12 16:15:30 +08:00
tools Merge branch 'feature/linux_esp_hw_support' into 'master' 2022-12-12 09:59:31 +08:00
.editorconfig refactor(editorconfig): Removed FreeRTOS tab rule 2022-09-23 12:53:33 +02:00
.flake8 tinyusb: Use TinyUSB from component registry 2022-11-02 08:24:43 +01:00
.gitignore Merge branch 'ci/cache_submodules' into 'master' 2022-07-14 20:34:34 +08:00
.gitlab-ci.yml build: Adds support for universal Clang toolchain 2022-11-23 13:25:16 +03:00
.gitmodules tinyusb: Use TinyUSB from component registry 2022-11-02 08:24:43 +01:00
.mypy.ini Add mypy check to pre-commit-config 2021-02-25 07:05:43 +00:00
.pre-commit-config.yaml precommit: update flake8 repo url to use github 2022-11-15 13:33:02 +08:00
.pylintrc style: ignore pylint too-many-instance-attributes error 2022-07-14 08:26:01 +08:00
.readthedocs.yml Whitespace: Automated whitespace fixes (large commit) 2020-11-11 07:36:35 +00:00
add_path.sh Whitespace: Automated whitespace fixes (large commit) 2020-11-11 07:36:35 +00:00
CMakeLists.txt build: Adds support for universal Clang toolchain 2022-11-23 13:25:16 +03:00
conftest.py ci: move more openocd scripts into pytest-embedded 2022-12-08 14:25:02 +08:00
CONTRIBUTING.md docs: make CONTRIBUTING.md readable on Github 2022-05-04 01:16:34 +02:00
export.bat tools: Remove tools that are not used by active ESP-IDF version. 2022-02-20 19:48:50 +01:00
export.fish Tools: Support ESP-IDF installed in system-wide shared directory for all users 2022-09-16 09:15:19 +02:00
export.ps1 tools: fix {install,export}.ps1 for IDF_PATH with spaces 2022-09-09 20:30:16 +02:00
export.sh Tools: Support ESP-IDF installed in system-wide shared directory for all users 2022-09-16 09:15:19 +02:00
install.bat Tools: Improve the Python package system 2022-01-17 16:54:36 +01:00
install.fish Tools: Fix silent failure about the incompatible Python 2022-02-16 18:44:13 +01:00
install.ps1 tools: fix {install,export}.ps1 for IDF_PATH with spaces 2022-09-09 20:30:16 +02:00
install.sh Tools: resolve symlinks in IDF_PATH when installing 2022-07-19 21:13:00 +02:00
Kconfig Merge branch 'refactor/rename_h2_to_h4' into 'master' 2022-11-09 19:19:43 +08:00
LICENSE Initial public version 2016-08-17 23:08:22 +08:00
pytest.ini pytest: check duplicates test case/script names 2022-12-08 09:49:12 +08:00
README_CN.md esp32h2: renaming esp32h2 to esp32h4 2022-11-08 17:05:33 +08:00
README.md esp32h2: renaming esp32h2 to esp32h4 2022-11-08 17:05:33 +08:00
sdkconfig.rename build: remove COMPILER_DISABLE_GCC8_WARNINGS, no longer relevant 2022-05-27 11:40:40 +07:00
SECURITY.md Add security policy guidelines 2022-06-24 11:11:38 +08:00
sonar-project.properties ci(sonarqube): pass "sonar.exclusions" in CI 2021-09-02 14:28:22 +08:00
SUPPORT_POLICY_CN.md docs: udpate CN translation for readme and build-system 2022-05-11 19:49:16 +08:00
SUPPORT_POLICY.md docs: udpate CN translation for readme and build-system 2022-05-11 19:49:16 +08:00

README.md

Espressif IoT Development Framework

ESP-IDF is the development framework for Espressif SoCs supported on Windows, Linux and macOS.

ESP-IDF Release Support Schedule

Support Schedule

ESP-IDF Release and SoC Compatibility

The following table shows ESP-IDF support of Espressif SoCs where alt text and alt text denote preview status and support, respectively. The preview support is usually limited in time and intended for beta versions of chips. Please use an ESP-IDF release where the desired SoC is already supported.

Chip v4.1 v4.2 v4.3 v4.4 v5.0 v5.1
ESP32 alt text alt text alt text alt text alt text alt text
ESP32-S2 alt text alt text alt text alt text alt text
ESP32-C3 alt text alt text alt text alt text
ESP32-S3 alt text alt text alt text Announcement
ESP32-C2 alt text alt text Announcement
ESP32-C6 alt text Announcement
ESP32-H2 beta1/2 alt text alt text alt text Announcement

Espressif SoCs released before 2016 (ESP8266 and ESP8285) are supported by RTOS SDK instead.

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