Compile fail only for tasmota32solo1 after update to 15.0.1

[andreagiaquinto]

Hello,
compile fail only for tasmota32solo1 after update tasmota to 15.0.1.
I can compile without any issues with tasmota 14.6.0.

sh: 1: None: not found
*** Error 127
*** [.pio/build/tasmota32solo1/firmware.bin] Explicit exit, status 2
========================= [FAILED] Took 64.83 seconds =========================

[andreagiaquinto]

Also tasmota32-zbbrdgpro failed to compile.
I am using PlatformIO 6.1.18.

idf_lib_copy(["checkprogsize"], [".pio/build/tasmota32-zbbrdgpro/firmware.elf"])
*** Copied compiled esp32 IDF libraries to Arduino framework ***
*** Starting Arduino compile tasmota32-zbbrdgpro with custom libraries ***
sh: 1: None: not found
Building .pio/build/tasmota32-zbbrdgpro/firmware.bin
*** Error 127
esptool.py v4.8.10
Creating esp32 image...
Merged 2 ELF sections
Successfully created esp32 image.

Read partitions from partitions/esp32_partition_app1856k_fs1344k.csv

Name, Type, SubType, Offset, Size, Flags

nvs data nvs 0x9000 0x5000
otadata data ota 0xe000 0x2000
safeboot app factory 0x10000 0xD0000
app0 app ota_0 0xE0000 0x1D0000
spiffs data spiffs 0x2B0000 0x150000

Will create filesystem with the following files:

/intelhex.be
/Sonoff_ZBPro.autoconf
/SonoffZBPro_coord_20220219.hex
/cc2652_flasher.be
/sonoff_zb_pro_flasher.be

Safeboot binary already in place

Offset   | File

• 0x1000 | /share/Tasmota/.pio/build/tasmota32-zbbrdgpro/bootloader.bin
• 0x8000 | /share/Tasmota/.pio/build/tasmota32-zbbrdgpro/partitions.bin
• 0xe000 | /root/.platformio/packages/framework-arduinoespressif32/tools/partitions/boot_app0.bin
• 0x10000 | /share/Tasmota/variants/tasmota/tasmota32-safeboot.bin
• 0xe0000 | /share/Tasmota/.pio/build/tasmota32-zbbrdgpro/firmware.bin
• 0x2b0000 | /share/Tasmota/.pio/build/tasmota32-zbbrdgpro/littlefs.bin

Will use custom upload command for flashing operation to add file system defined for this build target.

*** [.pio/build/tasmota32-zbbrdgpro/firmware.bin] Explicit exit, status 2
===================================================== [FAILED] Took 291.63 seconds =====================================================

Environment Status Duration

---

tasmota SUCCESS 00:01:07.556
tasmota-minimal SUCCESS 00:00:20.611
tasmota-sensors SUCCESS 00:01:20.045
tasmota-ir SUCCESS 00:00:34.386
tasmota32 SUCCESS 00:09:28.241
tasmota32solo1 FAILED 00:04:16.613
tasmota32-zbbrdgpro FAILED 00:04:51.634
================================================= 2 failed, 5 succeeded in 00:21:59.085 =================================================

[sfromis]

As I already told you on Discord

I had no trouble with solo1-based custom build with 15.0.1

Thus, there seems to be no general issue.

But you're still not posting any details about what you specifically did with your build.

[andreagiaquinto]

Platformio clean install solved the issues.
Thank you

[Noschvie]

Did you have a look to #23402

[andreagiaquinto]

Platformio clean install solved the issues.
Thank you

[Wintespe]

I am trying to compile Tasmota version 15.0.1 on a 64-bit Windows 10 system. To avoid problems with the compiler, I installed Visual Studio Code and PlatformIO fresh.
The following errors occurred when compiling:

Executing task: C:\Users\Win10\.platformio\penv\Scripts\platformio.exe run 

Processing tasmota (platform: https://github.com/tasmota/platform-espressif8266/releases/download/2025.05.00/platform-espressif8266.zip; framework: arduino; board: esp8266_1M)
----------------------------------------------------------------------------------------------------------------------------------------------------------------Verbose mode can be enabled via `-v, --verbose` option
-DCONFIG_TASMOTA_FLASHMODE_DOUT
ImportError: DLL load failed while importing zopfli: Das angegebene Modul wurde nicht gefunden.:
  File "C:\Users\Win10\.platformio\penv\Lib\site-packages\platformio\builder\main.py", line 167:
    env.SConscript(env.GetExtraScripts("pre"), exports="env")
  File "C:\Users\Win10\.platformio\packages\tool-scons\scons-local-4.8.1\SCons\Script\SConscript.py", line 620:
    return _SConscript(self.fs, *files, **subst_kw)
  File "C:\Users\Win10\.platformio\packages\tool-scons\scons-local-4.8.1\SCons\Script\SConscript.py", line 280:
    exec(compile(scriptdata, scriptname, 'exec'), call_stack[-1].globals)
  File "C:\Tsm\Tasmota-15.0.1\pio-tools\set_partition_table.py", line 12:
    import tasmotapiolib
  File "C:\Tsm\Tasmota-15.0.1\pio-tools\tasmotapiolib.py", line 155:
    import zopfli.gzip
  File "C:\Users\Win10\.platformio\penv\Lib\site-packages\zopfli\gzip.py", line 2:
    import zopfli.zopfli
================================================================== [FAILED] Took 3.61 seconds ==================================================================
Environment    Status    Duration
-------------  --------  ------------
tasmota        FAILED    00:00:03.613
============================================================ 1 failed, 0 succeeded in 00:00:03.613 ============================================================ 

 *  The terminal process "C:\Users\Win10\.platformio\penv\Scripts\platformio.exe 'run'" terminated with exit code: 1. 
*  Terminal will be reused by tasks, press any key to close it. #ecuting task: C:\Users\Win10\.platformio\penv\Scripts\platformio.exe run

In the same environment, Tasmota version 14.4.1 can be compiled without any problems.
The problem seems to occur since version 14.6.0. There I get a similar error message.

I then searched the system for a file zopfli*, nothing was found except a folder with the name zopfli. There are .PY files in there but no dll "s. Is a file missing or is the request incorrect?

I hope there is a solution to the problem.

[andreagiaquinto]

Hello @Wintespe,
I did uninstall platformio, remove folder (dot) .platformio and than fresh install platformio.
I my case is working but I am using debian.

Regards
Andrea

[Wintespe]

Thanks for the response. I have used a totally fresh Windows that has never seen VisualStudioCode and Platformio. There should be no difference between Win11 and Win10 in this case. However, I can also test it again under Win11. My Zopfli looks like this:

I am, however, surprised that:
in the same environment, Tasmota version 14.4.1 can be compiled without any problems.
There I get a similar error message.with version 14.6.0.

[Wintespe]

I have also tried it on Win11 with the same result. All different computers.
Btw zopfli-0.2.3.post1.dist-info is available on all systems.

[Wintespe]

I have now installed ProcMon by Mark Russinovich to see what happens. Zopfli is found without any problems.

11:43:22,2368069 python.exe 1880 Load Image C:\Users\Win10\.platformio\penv\Lib\site-packages\zopfli\zopfli.cp311-win_amd64.pyd SUCCESS Image Base: 0x7ffe43f40000, Image Size: 0x31000

Does anyone have any ideas what else I could look for?
On the Windows side, all operations are successful. So the problem should be in a script?

[barbudor]

You need to work in the platformio virtual env
In command line, go to your .platformio folder a'd execute
penv\Scripts\activate.cmd
Then run python and
import zopfli
import zopfli.gzip

You should get the same error as when building tasmota

I want to do the same on my computer and try to identify which DLL gets loaded using one of Mark's tools (can't remember if it's procmon or another)
But I'm away from my computer and will be unlikely able to do so before thursday evening

[Wintespe]

Here is the activation of Python and the result from the point of view of CMD.exe

Microsoft Windows [Version 10.0.19045.5965]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\Win10\.platformio\penv\Scripts>activate

(penv) C:\Users\Win10\.platformio\penv\Scripts>python
Python 3.11.7 (tags/v3.11.7:fa7a6f2, Dec  4 2023, 19:24:49) [MSC v.1937 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import zopfli
>>> import zopfli.gzip
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "C:\Users\Win10\.platformio\penv\Lib\site-packages\zopfli\gzip.py", line 2, in <module>
    import zopfli.zopfli
ImportError: DLL load failed while importing zopfli: Das angegebene Modul wurde nicht gefunden.
>>>

This is the output of ProcMon

15:41:19,9765623	python.exe	536	Load Image	C:\Users\Win10\.platformio\penv\Lib\site-packages\zopfli\zopfli.cp311-win_amd64.pyd	SUCCESS	Image Base: 0x7fff106c0000, Image Size: 0x31000
15:41:19,9776076	python.exe	536	Thread Create		SUCCESS	Thread ID: 5228
15:41:19,9802393	python.exe	536	Thread Create		SUCCESS	Thread ID: 5216

[andreagiaquinto]

Hello @Wintespe,
there is similar issues discussed at the following link:
https://stackoverflow.com/questions/58612306/how-to-fix-importerror-dll-load-failed-while-importing-win32api

[Wintespe]

Thanks for the link! There's a lot to read and understand there. It will take me a while to find out whether it addresses the problem.

[Wintespe]

@barbudor

I Tryed again import zopfli.gzip in the environment and get from ProcMon

17:07:26,2296207	python.exe	3384	Load Image	C:\Users\Win10\.platformio\penv\Lib\site-packages\zopfli\zopfli.cp311-win_amd64.pyd	SUCCESS	Image Base: 0x7ff895e30000, Image Size: 0x31000

17:07:26,2328183	python.exe	3384	Load Image	C:\Users\Win10\.platformio\python3\vcruntime140_1.dll	SUCCESS	Image Base: 0x7ff8975b0000, Image Size: 0xc000

If the dll vcruntime140_1.dll does not match (version ...) the error message dll not found may occur.

[barbudor]

Great find
Is that on the same machine ?
If you need that dll on other machine, Microsoft should have setup available to install various version of vcruntime

[joba-1]

iirc from many years ago, if you compiled and distributed a dll from c code with the ms compiler (like the zopfli dll) you also had to make sure the correct ms runtime is installed along your compiled dll. But no clear path on how to achieve that. I saw runtime install instructions in dll install readmes as well as dll installers automatically packaging and calling the runtime installer. So I guess it is somehow a zopfli installer problem you can get arround by manually installing the correct runtime version

[Jason2866]

You may try to install the other version of zopfli. Tasmota supports two variants
https://github.com/arendst/Tasmota/blob/development/pio-tools/tasmotapiolib.py

Once again a Windows only issue...

[Wintespe]

It looks like tasmotapiolib.py is also based on zopfli. However, calling it fails. So the problem persists.
In the meantime I have checked the whole thing on my main computer; it does not work.
All Windows machines that are tested report the same error. Some are real hardware and further than virtual machines with VirtualBox (Win10 and Win11)

[Jason2866]

tasmotapiolib.py is called in the buildprocess to compress the esp8266 firmware. Not a script to call alone.
And no judgement, just a fact Windows is a troublemaker.

[Wintespe]

Clearly, tasmotapiolib.py is used together with Zopfi for compression and does not run as a standalone program.

What remains is that Tasmota 14.6.0 and 15.0.1 have problems and Version 14.4.1 compiles without issues on the same machine with the identical environment. Firmware compression also works fine for 14.4.1.

I could now use WinMerge to find the differences. The Tasmota team can probably find them much more efficiently.

[barbudor]

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

[Wintespe]

@barbudor
Thanks for the hint.
vcruntime140.dll is not part of Windows and must either be present as a private file in a local application or globally in system32.

When installing Windows for the first time, the vcruntime140.dll compilation environment is not installed by default. It is not part of Windows!

To find the root cause for the problem I used ProcMon to find out that:

The Tasmota 14.4.1 compilation environment uses version 3.11.7 of Python.exe, located in the C:\Users\Win10.platformio\penv\Scripts folder, which uses a private version of vcruntime140.dll.

Tasmota 15.0.1 compilation environment uses C:\Users\Win10.platformio\python3\python.exe version 3.11.7. This Python interpreter does not use a local version and vcruntime140.dll must be installed separately. So there is an installation problem that is easy to solve with

https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

After the installation, all the tried Tasmota versions are now translating without errors., great.

[Wintespe]

Now I have tried to compile tasmota32solo1 Version 15.0.1
This is the result:

Executing task: C:\Users\Win10\.platformio\penv\Scripts\platformio.exe run --environment tasmota32solo1 

Processing tasmota32solo1 (board: esp32-solo1; framework: arduino; platform: https://github.com/tasmota/platform-espressif32/releases/download/2025.05.30/platform-espressif32.zip)
----------------------------------------------------------------------------------------------------------------------------------------------------------------Tool Manager: Installing https://github.com/pioarduino/registry/releases/download/0.0.1/mklittlefs-3.2.0.zip
Unpacking  [####################################]  100%
Tool Manager: tool-mklittlefs@3.2.0 has been installed!
Verbose mode can be enabled via `-v, --verbose` option
Nothing more to solidify
-DCONFIG_TASMOTA_FLASHMODE_DIO
*** use provided user_config_override.h as planned ***
*** use provided platformio_override.ini as planned ***
*** use provided platformio_tasmota_cenv.ini as planned ***
PIO called from VS Code extension
OS Platform: Windows
CONFIGURATION: https://docs.platformio.org/page/boards/espressif32/esp32-solo1.html
PLATFORM: Espressif 32 (2025.5.30) > Espressif Generic ESP32-solo1 >= 4M Flash, Tasmota 2880k Code/OTA, 320k FS
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
DEBUG: Current (cmsis-dap) External (cmsis-dap, esp-bridge, esp-prog, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa)
PACKAGES: 
 - framework-arduinoespressif32 @ 3.1.3+sha.138e9bb2
 - framework-espidf @ 3.50303.0 (5.3.3)
 - tool-cmake @ 3.30.2 
 - tool-esp-rom-elfs @ 2024.10.11
 - tool-esptoolpy @ 4.8.10
 - tool-ninja @ 1.10.2 
 - tool-scons @ 4.40801.0 (4.8.1)
 - toolchain-xtensa-esp-elf @ 13.2.0+20240530
Converting tasmota.ino
*** Compile Arduino IDF libs for tasmota32solo1 ***
*** Add "custom_sdkconfig" settings to IDF sdkconfig.defaults ***
Replace: CONFIG_ESPTOOLPY_FLASHMODE_QIO=y
 with: # CONFIG_ESPTOOLPY_FLASHMODE_QIO is not set
Replace: # CONFIG_ESPTOOLPY_FLASHMODE_DIO is not set
 with: CONFIG_ESPTOOLPY_FLASHMODE_DIO=y
Replace: CONFIG_ESPTOOLPY_FLASHFREQ_80M=y
 with: # CONFIG_ESPTOOLPY_FLASHFREQ_80M is not set
Replace: # CONFIG_ESPTOOLPY_FLASHFREQ_40M is not set
 with: CONFIG_ESPTOOLPY_FLASHFREQ_40M=y
Replace: CONFIG_ESPTOOLPY_FLASHFREQ="80m"
 with: CONFIG_ESPTOOLPY_FLASHFREQ="40m"
Replace: CONFIG_TWAI_ERRATA_FIX_BUS_OFF_REC=y
 with: # CONFIG_TWAI_ERRATA_FIX_BUS_OFF_REC is not set
Replace: CONFIG_TWAI_ERRATA_FIX_TX_INTR_LOST=y
 with: # CONFIG_TWAI_ERRATA_FIX_TX_INTR_LOST is not set
Replace: CONFIG_TWAI_ERRATA_FIX_RX_FRAME_INVALID=y
 with: # CONFIG_TWAI_ERRATA_FIX_RX_FRAME_INVALID is not set
Replace: CONFIG_TWAI_ERRATA_FIX_RX_FIFO_CORRUPT=y
 with: # CONFIG_TWAI_ERRATA_FIX_RX_FIFO_CORRUPT is not set
Replace: CONFIG_TWAI_ERRATA_FIX_LISTEN_ONLY_DOM=y
 with: # CONFIG_TWAI_ERRATA_FIX_LISTEN_ONLY_DOM is not set
Replace: CONFIG_SPIRAM=y
 with: # CONFIG_SPIRAM is not set
Replace: # CONFIG_FREERTOS_UNICORE is not set
 with: CONFIG_FREERTOS_UNICORE=y
Add: # CONFIG_SPIRAM is not set
Warning! Arduino framework as an ESP-IDF component doesn't handle the `variant` field! The default `esp32` variant will be used.
Reading CMake configuration...
-- Could NOT find Git (missing: GIT_EXECUTABLE) 
Hint: The project() command has not yet been called.  It sets up system-specific search paths.
-- git rev-parse returned ''
-- git rev-parse returned ''
-- Could not use 'git describe' to determine PROJECT_VER.
-- Building ESP-IDF components for target esp32
Dependencies lock doesn't exist, solving dependencies.

NOTICE: Skipping optional dependency: espressif/esp_hosted

NOTICE: Skipping optional dependency: espressif/esp_wifi_remote

..-- Configuring incomplete, errors occurred!

CMake Warning at C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/git_submodules.cmake:4 (message):
  Git executable was not found.  Git submodule checks will not be executed.
  If you have any build issues at all, start by adding git executable to the
  PATH and rerun cmake to not see this warning again.
Call Stack (most recent call first):
  C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/idf.cmake:41 (include)
  C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/project.cmake:29 (include)
  CMakeLists.txt:2 (include)


CMake Error at C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/build.cmake:582 (message):
  ERROR: "git" command was not found

Call Stack (most recent call first):
  C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/project.cmake:718 (idf_build_process)
  CMakeLists.txt:4 (project)

I do not have a local Git installation, therefore Could NOT find Git (missing: GIT_EXECUTABLE) ?

[andreagiaquinto]

@Wintespe I would install local git for windows:
https://github.com/git-for-windows/git/releases/download/v2.50.0.windows.1/Git-2.50.0-64-bit.exe
It is necessary to let the compiler script to download the dependency packages.

[Wintespe]

I have no intention in any way of installing Git on my machine. I don't think that should be necessary at all. If it is, then something is going wrong from my point of view. Furthermore, it seems to run on Linux without Git, I will check if necessary.

[Wintespe]

I have just successfully compiled it on Linux. No known Git on the machine. I have no idea yet what to do on Windows.
#23402 do not help, because the system is freshly installed.

[Wintespe]

Thnx for info. Since I don't use Github locally, it doesn't make sense for me to keep Git on the machine.

[sfromis]

Even if you wanted, you could not install Github locally, only some tools for easing operation with Github. Lots and lots of open source projects, including Tasmota and related libraries, are managed via the collaboration platform Github.

Git is simply a client which can be used for other things than just Github, including local usage, or interfacing with collaboration platform set up as alternatives to using Github. Even for a one-user local development setup, it could make sense to use Github for a systematic approach to fixes and versioning.

With projects hosted on Github, you should not even be surprised to see Git being involved in setup for builds. Just a completely normal and very common part of open source toolchains.

[joba-1]

the only strange thing with git and platformio is that it is needed but not provided as part of the toolchain like the compiler or python.

[Wintespe]

If Git is necessary, I'm right there with Joba-1 There would be no problems if Git were built into the toolchain. Surprisingly, Tasmota no longer compiles as it is now.. The messgage:

..-- Configuring incomplete, errors occurred!

CMake Warning at C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/git_submodules.cmake:4 (message):
  Git executable was not found.  Git submodule checks will not be executed.
  If you have any build issues at all, start by adding git executable to the
  PATH and rerun cmake to not see this warning again.
Call Stack (most recent call first):
  C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/idf.cmake:41 (include)
  C:/Users/Win10/.platformio/packages/framework-espidf/tools/cmake/project.cmake:29 (include)
  CMakeLists.txt:2 (include)

is unclear if you don't know about Git.

[joba-1]

if you know git then you understand the mentioned submodule check is not needed if you know your files are consistent by other means. It is flagged as just a warning so it is unclear to me why the process stops.
Anyways, to me it looks more like an espressif problem. Would need windows to check.