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: https://www.github.com/neonious/memtest
Our advertisment block:
Please take a look at www.lowjs.org for Node.JS on ESP32: scalable, feature rich programming of microcontrollers done easily
Please take a look at www.neonious.com 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 www.neonious-basics.com for interesting news and blog posts which educate you about electronics
Espressif IoT Development Framework
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:
- Getting Started Guide for the stable ESP-IDF version
- Getting Started Guide for the latest (master branch) ESP-IDF version
Finding a Project
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.
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
- 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.
?to see a help screen. Enter key exits the help screen.
- Use Space key, or
Nkeys to enable (Yes) and disable (No) configuration items with checkboxes "
?while highlighting a configuration item displays help about that item.
/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.
-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 esptool.py 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
You don't need to run
make all before running
make flash will automatically rebuild anything which needs it.
Viewing Serial Output
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.)
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
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
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.
The esp32.com forum is a place to ask questions and find community resources.
Check the Issues section on github if you find a bug or have a feature request. Please check existing Issues before opening a new one.
If you're interested in contributing to ESP-IDF, please check the Contributions Guide.