Crash_Override/OVMS3-idf
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
Espressif IoT Development Framework. Official development framework for ESP32.
61 commits 10 branches 75 tags 114 MiB
C 91.5%
Python 3.7%
C++ 2.7%
CMake 0.7%
Assembly 0.5%
Other 0.7%
Go to file
Ivan Grokhotkov 2cd1da31f9 Merge branch 'bugfix/dram_attr' into 'master' 
fix DRAM_ATTR attribute

Variables marked with DRAM_ATTR were not placed in any specific section and were appended to the last section, causing some errors at binary file generation stage.
This change places contents of .dram1 section into .dram0.data.
Also removes .iram1pro/.iram1app/.dram1pro/.dram1app which weren't used anywhere.

See merge request !23
2016-08-25 10:19:17 +08:00
bin esptool.py: Set higher baud rates on ESP32 2016-08-22 18:44:41 +08:00
components Merge branch 'bugfix/dram_attr' into 'master' 2016-08-25 10:19:17 +08:00
docs docs: update linux getting started guide 2016-08-24 11:17:15 +08:00
make Makefile: Don't re-build libraries or re-link ELF files if nothing has changed in the component 2016-08-24 13:25:06 +08:00
tools Use IDF_PATH instead of SDK_PATH for the environment variable pointing to esp-idf 2016-08-19 15:01:49 +08:00
.gitignore Initial public version 2016-08-17 23:08:22 +08:00
.gitlab-ci.yml CI: Pass IDF_PATH to build_system_tests.sh 2016-08-24 13:31:33 +08:00
.gitmodules gitlab-ci: initial version 2016-08-22 17:37:47 +08:00
Kconfig Standardise remaining uses of SDK to ESP-IDF 2016-08-19 15:01:15 +08:00
LICENSE Initial public version 2016-08-17 23:08:22 +08:00
README.buildenv Makefile: Rename $(vecho) to $(summary), add new $(details) for echoing details when V=1 2016-08-24 13:25:06 +08:00
README.md make: 'make all' default target builds everything, 'make flash' flashes everything 2016-08-18 21:42:37 +08:00

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.