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
11,081 Commits 20 Branches 148 Tags 384 MiB
C 95.6%
Python 2.1%
C++ 1.2%
CMake 0.7%
Assembly 0.3%
85ca721867
Go to file
Armando 85ca721867 spi: fix issue with closing DMA before CPU reset
2020-10-14 22:05:21 +08:00
.github github: Sync PRs to JIRA as well 2019-03-14 14:29:46 +11:00
components spi: fix issue with closing DMA before CPU reset 2020-10-14 22:05:21 +08:00
docs build system: Also get IDF version from annotated tags only 2020-10-07 13:55:53 +11:00
examples Merge branch 'feature/esp_spp_stop_srv_v4.0' into 'release/v4.0' 2020-09-04 20:00:41 +08:00
make build system: Also get IDF version from annotated tags only 2020-10-07 13:55:53 +11:00
tools ci: Check version tags are always annotated 2020-10-07 13:55:53 +11:00
.editorconfig cmake: Use cmake_lint project, tidy up all CMake source files 2018-04-30 09:59:20 +10:00
.flake8 ESP Local Control Feature Added 2019-07-03 21:31:04 +05:30
.gitignore tools: new installer for Windows 2019-07-01 18:08:02 +02:00
.gitlab-ci.yml ci: remove using IDF_XTENSA_TOOLCHAIN_URL because there are idf_tools.json and multi-target support 2020-02-10 18:38:23 +07:00
.gitmodules tools: Add a script for switching to real submodules in forks 2019-07-05 11:12:06 +07:00
.readthedocs.yml docs: Remove building of zipped HTML docs from build process and consequently from Downloads as many users don't use that. We are still providing PDF documentation for people who prefer viewing docs off-line. Removal of this build step is expected to save almost 10 minutes of build time and resolve issue of build failures because of hitting 40 min build time limit on Read The Docs. 2019-07-08 13:19:56 +08:00
.travis.yml Check the Python coding style 2018-11-26 15:02:27 +01:00
add_path.sh tools: {install,export}.{bat,sh} tools 2019-07-01 14:51:44 +02:00
CMakeLists.txt cmake: error out on building in IDF_PATH root dir 2020-04-08 19:56:57 +08:00
CONTRIBUTING.rst docs: This is a quick reference of more than a dozen and-ons and extensions prepared over the last two years to add contents, improve look & feel and cut on maintenance of the ESP-IDF documentation. 2019-02-17 20:32:50 +01:00
export.bat tools: {install,export}.{bat,sh} tools 2019-07-01 14:51:44 +02:00
export.sh tools: export.sh: fix compatibility with dash shell 2020-06-24 10:37:51 +02:00
install.bat tools: install.bat: bail out if idf_tools.py call fails 2019-07-23 06:20:52 +02:00
install.sh tools: {install,export}.{bat,sh} tools 2019-07-01 14:51:44 +02:00
Kconfig Docs: Encourage to used Python 3 2020-02-26 09:01:42 +01:00
LICENSE Initial public version 2016-08-17 23:08:22 +08:00
README.md Added -r flag to pip install command from file 2019-08-15 14:23:49 +02:00
requirements.txt idf.py: Add support for action specific options 2019-06-03 13:07:02 +02:00
sdkconfig.rename Rename Kconfig options (root) 2019-05-21 09:09:01 +02:00
SUPPORT_POLICY.md docs: Add ESP-IDF support period policy 2019-10-29 16:26:13 +11:00

README.md

Espressif IoT Development Framework

Documentation Status

ESP-IDF is the official development framework for the ESP32 chip.

Developing With ESP-IDF

Setting Up ESP-IDF

See setup guides for detailed instructions to set up the 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 Getting Started guide for a full list of required steps with details.)

  • Install host build dependencies mentioned in Getting Started guide.
  • Add tools/ directory to the PATH
  • Run python -m pip install -r requirements.txt to install Python dependencies

Configuring the Project

idf.py menuconfig

  • Opens a text-based configuration menu for the project.
  • Use up & down arrow keys to navigate the menu.
  • Use Enter key to go into a submenu, Escape key to go out or to exit.
  • Type ? to see a help screen. Enter key exits the help screen.
  • Use Space key, or Y and N keys to enable (Yes) and disable (No) configuration items with checkboxes "[*]"
  • Pressing ? while highlighting a configuration item displays help about that item.
  • Type / to search the configuration items.

Once done configuring, press Escape multiple times to exit and say "Yes" to save the new configuration when prompted.

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 the ESP32. 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