Error trying to compile ESP32_GENERIC firmware? #19043

Nodi-Rubrum · 2026-04-05T06:06:16Z

Nodi-Rubrum
Apr 5, 2026

Trying to learn how to create a custom firmware image for ESP32. Error trying to compile ESP32_GENERIC firmware? Error...

# make
-- Configuring incomplete, errors occurred!
HINT: newlib component has been renamed to esp_libc. Any `REQUIRES newlib` can simply be deleted as esp_libc is REQUIRED by default.
cmake failed with exit code 1, output of the command is in the /root/micropython/ports/esp32/build/log/idf_py_stderr_output_13085 and /root/micropython/ports/esp32/build/log/idf_py_stdout_output_13085

Here is what I did in total to create the environment, and attempting to complete the generic firmware image...

# apt update
# apt install nala
# nala install build-essential git python3 libffi-dev pkg-config python3-venv cmake

# cd /root
# git clone https://github.com/micropython/micropython.git

# cd ~/micropython
# git submodule update --init --recursive

# mkdir -p ~/esp
# cd ~/esp
# git clone --recursive https://github.com/espressif/esp-idf.git
# cd ~/esp/esp-idf
# ./install.sh all
# . ./export.sh

# cd ~/micropython
# make -C mpy-cross

# cd ~/micropython/ports/esp32
# make clean
# make
Use make V=1 or set BUILD_VERBOSE in your environment to increase build verbosity.
Executing action: all (aliases: build)
Running cmake in directory /root/micropython/ports/esp32/build-ESP32_GENERIC
Executing "cmake -G 'Unix Makefiles' -B /root/micropython/ports/esp32/build-ESP32_GENERIC -DPYTHON_DEPS_CHECKED=1 -DPYTHON=/root/.espressif/python_env/idf6.1_py3.13_env/bin/python -DESP_PLATFORM=1 -DMICROPY_BOARD=ESP32_GENERIC -DMICROPY_BOARD_DIR=/root/micropython/ports/esp32/boards/ESP32_GENERIC -DCCACHE_ENABLE=False /root/micropython/ports/esp32"...
-- IDF_TARGET not set, using default target: esp32
-- Found Git: /usr/bin/git (found version "2.47.3")
-- Component directory /root/esp/esp-idf/components/idf_test does not contain a CMakeLists.txt file. No component will be added
-- Minimal build - OFF
-- The C compiler identification is GNU 15.2.0
-- The CXX compiler identification is GNU 15.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /root/.espressif/tools/xtensa-esp-elf/esp-15.2.0_20251204/xtensa-esp-elf/bin/xtensa-esp32-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /root/.espressif/tools/xtensa-esp-elf/esp-15.2.0_20251204/xtensa-esp-elf/bin/xtensa-esp32-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /root/.espressif/tools/xtensa-esp-elf/esp-15.2.0_20251204/xtensa-esp-elf/bin/xtensa-esp32-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32
NOTICE: Skipping optional dependency: espressif/tinyusb
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_wifi_remote
NOTICE: Processing 3 dependencies:
NOTICE: [1/3] espressif/lan867x (1.0.3)
NOTICE: [2/3] espressif/mdns (1.1.0)
NOTICE: [3/3] idf (6.1.0)
-- ESP-TEE is currently supported only on the esp32c6;esp32h2;esp32c5;esp32c61 SoCs
NOTICE: Skipping optional dependency: espressif/tinyusb
NOTICE: Skipping optional dependency: espressif/esp_hosted
NOTICE: Skipping optional dependency: espressif/esp_wifi_remote
CMake Error at /root/esp/esp-idf/tools/cmake/build.cmake:380 (message):
  Failed to resolve component 'newlib' required by component 'main': unknown
  name.
Call Stack (most recent call first):
  /root/esp/esp-idf/tools/cmake/build.cmake:423 (__build_resolve_and_add_req)
  /root/esp/esp-idf/tools/cmake/build.cmake:768 (__build_expand_requirements)
  /root/esp/esp-idf/tools/cmake/project.cmake:773 (idf_build_process)
  CMakeLists.txt:70 (project)


-- Configuring incomplete, errors occurred!
HINT: newlib component has been renamed to esp_libc. Any `REQUIRES newlib` can simply be deleted as esp_libc is REQUIRED by default.
cmake failed with exit code 1, output of the command is in the /root/micropython/ports/esp32/build-ESP32_GENERIC/log/idf_py_stderr_output_13397 and /root/micropython/ports/esp32/build-ESP32_GENERIC/log/idf_py_stdout_output_13397
-e See https://github.com/micropython/micropython/wiki/Build-Troubleshooting
make: *** [Makefile:77: all] Error 1

I tried the following, based on some google search results...

# pip install --upgrade idf-component-manager
# rm -rf ~/.cache/Espressif/
# rm -rf ~/micropython/ports/esp32/build-ESP32_GENERIC

Then again tried to execute the 'make' but same error as noted above. Environment is Debian 13.4. Any assistance greatly appreciated!

Josverl · 2026-04-05T08:57:36Z

Josverl
Apr 5, 2026
Collaborator Sponsor

I only take the lazy path

uv tool install mpbuild , mpbuild build ESP32_GENERIC

or you can re-use the logic built into to the ci workflows and scripts

.github/workflows/ports_esp32.yml
source tools/ci.sh

if you want to DIY, I would recommend to avoid :

git submodule update --init --recursive

and use the procedure docuemented in ports/esp32/README.md

$ cd ports/esp32
$ make submodules
$ make

0 replies

easytarget · 2026-04-05T10:04:26Z

easytarget
Apr 5, 2026

NOTICE: [3/3] idf (6.1.0)

It looks like you are running the a pre-release (LATEST/HEAD) version of the ESP-IDF, V6.0 was only released 2 weeks ago.

ESP-IDF 6+ is not (yet!) supported for MicroPython; the highest supported version is 5.4.2, see:
https://github.com/micropython/micropython/blob/master/ports/esp32/README.md#setting-up-esp-idf-and-the-build-environment

V6 of the ESP-IDF has some (breaking) changes from V5, so it is no wonder that this does not yet compile.

You will need to use one of the supported IDF's listed there, and wait for IDF 6+ support to arrive in the micropython port.

0 replies

shariltumin · 2026-04-05T10:44:37Z

shariltumin
Apr 5, 2026

I can compile MicroPython for ESP32 with ESP-IDF up to version 5.5.1

git clone -b v5.5.1 --recursive https://github.com/espressif/esp-idf.git

0 replies

Nodi-Rubrum · 2026-04-05T17:14:42Z

Nodi-Rubrum
Apr 5, 2026
Author

A bridge too far... 6.1. Using 5.5.1 compile of ESP32 generic seems successful, now to complete flash of device. Thanks everyone.

0 replies

Nodi-Rubrum · 2026-04-06T02:52:29Z

Nodi-Rubrum
Apr 6, 2026
Author

One more question... when I successfully compiled the generic firmware, I see two bin files, one called micropython, one called firmware, can some qualify the difference? The one entitled firmware seems be the correct one, because when I flashed the one called micropython, it loaded fine but the ESP32 board was in an endless reset loop as a result.

1 reply

Josverl Apr 6, 2026
Collaborator Sponsor

firmware.bin = <bootloader>+<partition table>+<micropython.bin>
micropython.bin = <MicroPython>+<frozen .mpy modules>

in essence; firmware.bin is created by esptool merge-bin to allow for simpler flashing

Bharath-970 · 2026-04-13T02:30:32Z

Bharath-970
Apr 13, 2026

This error is actually coming from an ESP-IDF version mismatch.

You’re using IDF 6.1, but MicroPython’s ESP32 port still expects older components (like newlib), which were renamed to esp_libc in newer IDF versions.

So even though your setup looks correct, the build system is pulling in incompatible components.

Fix is to use a compatible IDF version (e.g. v5.2):

git clone -b v5.2 --recursive https://github.com/espressif/esp-idf.git

Then reinstall + rebuild:
./install.sh all
. ./export.sh
make clean
make

This kind of issue is tricky because the actual failure (“newlib not found”) is just a symptom of version mismatch, and CI/build logs don’t always make that obvious.

I’ve been working on a small tool that extracts these kinds of root causes from noisy CI logs automatically — happy to share if useful.

0 replies

MicroPython

Error trying to compile ESP32_GENERIC firmware? #19043

Uh oh!

Uh oh!

Nodi-Rubrum Apr 5, 2026

Replies: 6 comments · 1 reply

Uh oh!

Uh oh!

Josverl Apr 5, 2026 Collaborator Sponsor

Uh oh!

Uh oh!

easytarget Apr 5, 2026

Uh oh!

shariltumin Apr 5, 2026

Uh oh!

Uh oh!

Nodi-Rubrum Apr 5, 2026 Author

Uh oh!

Nodi-Rubrum Apr 6, 2026 Author

Uh oh!

Uh oh!

Josverl Apr 6, 2026 Collaborator Sponsor

Uh oh!

Bharath-970 Apr 13, 2026

Nodi-Rubrum
Apr 5, 2026

Replies: 6 comments 1 reply

Josverl
Apr 5, 2026
Collaborator Sponsor

easytarget
Apr 5, 2026

shariltumin
Apr 5, 2026

Nodi-Rubrum
Apr 5, 2026
Author

Nodi-Rubrum
Apr 6, 2026
Author

Josverl Apr 6, 2026
Collaborator Sponsor

Bharath-970
Apr 13, 2026