Keine Beschreibung

Ivan Grokhotkov 9938f512f3 peripheral structure headers: move volatile keyword from members to typedef vor 9 Jahren
components 9938f512f3 peripheral structure headers: move volatile keyword from members to typedef vor 9 Jahren
docs 7c58c1e06b Build system: Allow components to add to the global CFLAGS via Makefile.projbuild vor 9 Jahren
make f703acd344 Adding -fstrict-volatile-bitfields to the CFLAGS/CXXFLAGS. Without this, gcc tries to access bitfields using the smallest possible methods (eg l8i to vor 9 Jahren
tools 7c58c1e06b Build system: Allow components to add to the global CFLAGS via Makefile.projbuild vor 9 Jahren
.gitignore bd6ea4393c Initial public version vor 9 Jahren
.gitlab-ci.yml 7fade89fb6 Merge branch 'bugfix/github_deploy' into 'master' vor 9 Jahren
.gitmodules 96852d49c2 Load esptool.py from submodule, currently WIP esptool.py v2.0 vor 9 Jahren
Kconfig 9ec0e1545d Standardise remaining uses of SDK to ESP-IDF vor 9 Jahren
LICENSE bd6ea4393c Initial public version vor 9 Jahren
README.md b9a853c903 README: Add Resources section with some links vor 9 Jahren
add_path.sh bab3faba58 add_path.sh: Use non-bash-specific instructions vor 9 Jahren

README.md

Using Espressif IoT Development Framework with the ESP32

Prerequisites

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.

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

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.

Resources