Acasă Explorează Ajutor
Autentificare
RT-Thread-packages
/
esp-idf
oglindă de https://github-proxy.rt-thread.io/RT-Thread-packages/esp-idf.git
2
0
Bifurcare 0
Fisiere Probleme 0 Wiki

Fără Descriere

Arbore: a64acef06f
Ramuri Etichete
esp-idf
ZIP TAR.GZ
baohongde a64acef06f components/bt: Make sleep avaliable in hli(for future use) 5 ani în urmă
.github df61488e54 build system: Also get IDF version from annotated tags only 5 ani în urmă
components a64acef06f components/bt: Make sleep avaliable in hli(for future use) 5 ani în urmă
docs 65f1be59ad Merge branch 'bugfix/idf_py_disable_cmake_warnings_default_v4.1' into 'release/v4.1' 5 ani în urmă
examples a8035d21ef ble_mesh: add ble mesh coex test example 5 ani în urmă
make df61488e54 build system: Also get IDF version from annotated tags only 5 ani în urmă
tools d925b564cd esp32: Switch SPIRAM stack in esp_restart_noos() to internal stack 5 ani în urmă
.editorconfig 88df8fd293 cmake: Use cmake_lint project, tidy up all CMake source files 7 ani în urmă
.flake8 01887f71e7 Update kconfiglib to upstream version and replace mconf-idf 6 ani în urmă
.gitignore dfafa98253 Use component manager if available as python package 6 ani în urmă
.gitlab-ci.yml e552ea0d9c ci: use HTTPS for cloning in IT jobs 5 ani în urmă
.gitmodules dfafa98253 Use component manager if available as python package 6 ani în urmă
.readthedocs.yml 363f3e8311 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. 6 ani în urmă
CMakeLists.txt 40af109144 cmake: error out on building in IDF_PATH root dir 5 ani în urmă
CONTRIBUTING.rst ed0db52f74 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. 7 ani în urmă
Kconfig 5f2d918437 bootloader: Set the bootloader optimization level separately to the app 6 ani în urmă
LICENSE bd6ea4393c Initial public version 9 ani în urmă
README.md 7da1603a1c Fix the setup instructions in the main README 5 ani în urmă
README_CN.md 18183871de add zh_CN translation of README in esp-idf repo 6 ani în urmă
SUPPORT_POLICY.md 806229492e add chinese translation for support period policy 6 ani în urmă
SUPPORT_POLICY_CN.md 806229492e add chinese translation for support period policy 6 ani în urmă
add_path.sh 12b6da0388 tools: {install,export}.{bat,sh} tools 6 ani în urmă
export.bat 12b6da0388 tools: {install,export}.{bat,sh} tools 6 ani în urmă
export.ps1 79dd142ab8 tools: add install.ps1, export.ps1 6 ani în urmă
export.sh b85f877817 tools: export.sh: fix compatibility with dash shell 5 ani în urmă
install.bat f38c1c18a8 tools: install.bat: bail out if idf_tools.py call fails 6 ani în urmă
install.ps1 79dd142ab8 tools: add install.ps1, export.ps1 6 ani în urmă
install.sh 12b6da0388 tools: {install,export}.{bat,sh} tools 6 ani în urmă
requirements.txt dfafa98253 Use component manager if available as python package 6 ani în urmă
sdkconfig.rename 4fdaeb6b6e cmake: Add new compiler optimization levels definitions 6 ani în urmă

README.md

Espressif IoT Development Framework

Documentation Status

ESP-IDF is the official development framework for the ESP32 chip 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:

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