ESP-IDF modified to use dlmalloc
Branch: master
Clone or download
Pull request Compare This branch is 4 commits ahead, 194 commits behind espressif:master.
neoniousTR whoops, did not use locks correctly!
fixed this. random crashes gone
Latest commit ded0dfa Dec 28, 2018
Type Name Latest commit message Commit time
Failed to load latest commit information.
components whoops, did not use locks correctly! Dec 28, 2018
examples Merge branch 'feature/example_defconfig_ci' into 'master' Dec 21, 2018
make cmake: fix regression with linux make builds Dec 17, 2018
tools cmake: fix unable to start confserver on windows Dec 23, 2018
.editorconfig cmake: Use cmake_lint project, tidy up all CMake source files Apr 29, 2018
.flake8 tools: Fix the Python coding style Dec 19, 2018
.gitignore cmake: separate app from idf lib project Nov 27, 2018
.gitlab-ci.yml Merge branch 'test/add_case_to_detect_ds2ds_issue' into 'master' Dec 13, 2018
.gitmodules examples: generic cmake support examples Nov 27, 2018
.travis.yml Check the Python coding style Nov 26, 2018
CMakeLists.txt build: Fix a warning from git describe Dec 18, 2018
CONTRIBUTING.rst docs: Add "Creating Examples" docs page, template example README Jun 14, 2018
Kconfig build system: support for multiple targets Nov 11, 2018
LICENSE Initial public version Aug 17, 2016 Update Dec 27, 2018 Fix reuse the script Nov 28, 2018
requirements.txt tools: install pyparsing using pip Nov 22, 2018

ESP-IDF modified to use dlmalloc

The default memory allocator in ESP-IDF is self made by Espressif (at least so it seems). It is not very fast, and becomes very slow when memory gets fragmented. This problem becomes evident when using SPI RAM.

This is a fork of ESP-IDF which was modified to use dlmalloc, an industry standard memory allocator. It is almost twice as fast as the default memory allocator, and does not slow down notably with fragmented memory.

Following featues are not yet re-implemented:

  • Heap poisening
  • Heap task tracking

Small test application:

Our advertisment block:

  • Please take a look at for Node.JS on ESP32: scalable, feature rich programming of microcontrollers done easily

  • Please take a look at for a great microcontroller board with Ethernet and Wifi wifi an integrated IDE + debugger on board and more!

  • Please take a look at our blog for interesting news and blog posts which educate you about electronics

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:

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:

Configuring the Project

make 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

make -j4 all

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

NOTE: The -j4 option causes make to run 4 parallel jobs. This is much faster than the default single job. The recommended number to pass to this option is -j(number of CPUs + 1).

Flashing the Project

When the build finishes, it will print a command line to use to flash the chip. However you can also do this automatically by running:

make -j4 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 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:

make -j4 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:

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

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

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 the number of CPU cores in your system, plus one.)

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 0x8000 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/en/api-guides/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.