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
1,621 Commits 20 Branches 148 Tags 384 MiB
C 95.6%
Python 2.1%
C++ 1.2%
CMake 0.7%
Assembly 0.3%
e9f8e03309
Go to file
Ivan Grokhotkov e9f8e03309 Merge branch 'feature/JSON_Float' into 'master' 
Add float format process

Add float format process

See merge request !390
2017-01-10 13:01:43 +08:00
components Merge branch 'feature/JSON_Float' into 'master' 2017-01-10 13:01:43 +08:00
docs Merge branch 'feature/btdm_common_api' into 'master' 2017-01-09 11:33:57 +08:00
examples Merge branch 'feature/openssl' into 'master' 2017-01-10 12:01:40 +08:00
make build system: Fix sdkconfig.defaults file preventing menuconfig changes 2017-01-09 15:19:23 +11:00
tools unity: fix testcase initializer for compiling with C++ 2017-01-06 14:56:02 +08:00
.gitignore add unit tests to esp-idf 2016-11-22 14:45:50 +08:00
.gitlab-ci.yml CI: fix bug that test report job failed 2017-01-03 14:07:00 +08:00
.gitmodules components/coap: Add libcoap library as submodule 2016-12-30 15:05:26 +08:00
add_path.sh add_path.sh: Use non-bash-specific instructions 2016-09-12 18:39:20 +10:00
CONTRIBUTING.rst docs: Hyperlinks to guides 2016-11-21 10:24:12 +08:00
Kconfig build system: fix setting C**FLAGS from project makefile 2016-10-20 17:17:54 +08:00
LICENSE Initial public version 2016-08-17 23:08:22 +08:00
README.md README: Add a note about parallel builds 2017-01-03 10:59:11 +11:00

README.md

Using Espressif IoT Development Framework with the ESP32

alt text

Setting Up ESP-IDF

In the docs directory you will find per-platform setup guides:

Finding A Project

As well as the esp-idf-template project mentioned in the setup guide, 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:

Configuring your project

make menuconfig

Compiling your project

make all

... will compile app, bootloader and generate a partition table based on the config.

Flashing your project

When make all finishes, it will print a command line to use esptool.py to flash the chip. However you can also do this from make by running:

make flash

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 make menuconfig.

You don't need to run make all before running make flash, make flash will automatically rebuild anything which needs it.

Viewing Serial Output

The make monitor target will use the already-installed miniterm (a part of pyserial) to display serial output from the ESP32 on the terminal console.

Exit miniterm by typing Ctrl-].

To flash and monitor output in one pass, you can run:

make flash monitor

Compiling & Flashing Just the App

After the initial flash, you may just want to build and flash just your app, not the bootloader and partition table:

  • make app - build just the app.
  • make app-flash - flash just the app.

make app-flash will automatically rebuild the app if it needs it.

(There's no downside to reflashing the bootloader and partition table each time, if they haven't changed.)

Parallel Builds

esp-idf supports compiling multiple files in parallel, so all of the above commands can be run as make -jN where N is the number of parallel make processes to run (generally N should be equal to or one more than the number of CPU cores in your system.)

Multiple make functions can be combined into one. For example: to build the app & bootloader using 5 jobs in parallel, then flash everything, and then display serial output from the ESP32 run:

make -j5 flash monitor

The Partition Table

Once you've compiled your project, the "build" directory will contain a binary file with a name like "my_app.bin". This is an ESP32 image binary that can be loaded by the bootloader.

A single ESP32's flash can contain multiple apps, as well as many different kinds of data (calibration data, filesystems, parameter storage, etc). For this reason a partition table is flashed to offset 0x4000 in the flash.

Each entry in the partition table has a name (label), type (app, data, or something else), subtype and the offset in flash where the partition is loaded.

The simplest way to use the partition table is to make menuconfig and choose one of the simple predefined partition tables:

  • "Single factory app, no OTA"
  • "Factory app, two OTA definitions"

In both cases the factory app is flashed at offset 0x10000. If you make partition_table then it will print a summary of the partition table.

For more details about partition tables and how to create custom variations, view the docs/partition-tables.rst file.

Erasing Flash

The make 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 make erase_flash.

This can be combined with other targets, ie make erase_flash flash will erase everything and then re-flash the new app, bootloader and partition table.

Resources