ESP32-C3 Compile to Target Failure

Any bugs you encounter with Flowcode should be discussed here.
Post Reply
liudeqiang_2008
Posts: 52
http://meble-kuchenne.info.pl
Joined: Wed Jan 12, 2022 8:25 am
Has thanked: 10 times
Been thanked: 1 time

Flowcode v10 ESP32-C3 Compile to Target Failure

Post by liudeqiang_2008 »

Hello,
I have tested 3 ESP32 boards:

ESP32-DevKitC(ESP32-WROOM-32E) --- Compile to Target success!
ESP32-S3-DevKitC-1 v1.0 --- Compile to Target success!
ESP32-C3-DevKitC-02 v1.1 --- Compile to Target failure...

Compile log:
-----------------------
Target folder: \\01_EmbeddedDesign\Flowcode\ESP32-C3-DevKitC-02
Source name: \\01_EmbeddedDesign\Flowcode\ESP32-C3-DevKitC-02\RGBLED_TEST01.fcfx
Title:
Description:
Device: ESP.ESP32.ESP32-C3_DevKitC
Generated by: Flowcode v10.1.2.40
Date: Friday, July 25, 2025 11:25:59
Users: 1

NOT FOR COMMERCIAL USE
https://www.flowcode.co.uk
Using FCD settings for compiler
Launching the compiler...
C:\ProgramData\MatrixTSL\FlowcodeV10\FCD\ESP\Batch\esp32_build.bat "D:\FC_ESP\\" "RGBLED_TEST01"
"\\01_EmbeddedDesign\Flowcode\ESP32-C3-DevKitC-02\" esp32_c3_sdkconfig esp32c3
'\\01_EmbeddedDesign\Flowcode\ESP32-C3-DevKitC-02'
Ϊ ǰĿ¼ · CMD.EXE
UNC · ֧ ֡ Ĭ ֵ Ϊ Windows Ŀ¼

C:\Windows>REM CRC: 0796FC1E6A776AF9156B257209C35258CE7C28B3EC20AEA2C632DB392A0E4BFD5B3F53B21811978F7B21FE4085045A7E774D1D3D69D8A99EE7320EAE740A5DB60228F42835EF5B88138FDEE58A4EE9C3A4BAF1B34E38B68E0C3CAEE8E7DA6987B808018476405B65B199900461C78937B42DEF8219F63A24580137A2F6C8FDB7553324EFF791947E8AB6FFD612B81BAA97C798A8F1CFC189DE5D38517747C774AF2DD6F839BAECF83F7F994C7164CE77868F480396BDEF2F2C3050DA273BE4EE69F15C302679453617F9EA00A6A8712D05E485F25DB02304E4565E63FDA312627DD474674123A97D

C:\Windows>REM REVISION: 15.0

C:\Windows>REM GUID: 955EA920-4961-4C53-BA6B-EF4AF66BB4C2

C:\Windows>REM DATE: 07\04\2025

C:\Windows>REM DIR: FCD\ESP\Batch\esp32_build.bat
Creating python config file
Creating menuconfig link file
.
============================== Toolchain Check ==============================
Python 3.11.2
git version 2.44.0.windows.1
ESP toolchain found at "D:\FC_ESP\frameworks\esp-idf-v5.3.1\"
=============================================================================
.
Building: RGBLED_TEST01 ...
fatal: not a git repository (or any of the parent directories): .git
IDF Version: ...
Checking Python compatibility
Setting IDF_PATH: D:\FC_ESP\frameworks\esp-idf-v5.3.1

Adding ESP-IDF tools to PATH...
Not using an unsupported version of tool cmake found in PATH: 3.28.1.
WARNING: The following issue occurred while accessing the ESP-IDF version file in the Python environment: [Errno 2] No such file or directory: 'D:\\FC_ESP\\esp-tools\\python_env\\idf5.3_py3.11_env\\idf_version.txt'. (Diagnostic information. It can be ignored.)
D:\FC_ESP\esp-tools\tools\xtensa-esp-elf-gdb\14.2_20240403\xtensa-esp-elf-gdb\bin
D:\FC_ESP\esp-tools\tools\riscv32-esp-elf-gdb\14.2_20240403\riscv32-esp-elf-gdb\bin
D:\FC_ESP\esp-tools\tools\xtensa-esp-elf\esp-13.2.0_20240530\xtensa-esp-elf\bin
D:\FC_ESP\esp-tools\tools\riscv32-esp-elf\esp-13.2.0_20240530\riscv32-esp-elf\bin
D:\FC_ESP\esp-tools\tools\esp32ulp-elf\2.38_20240113\esp32ulp-elf\bin
D:\FC_ESP\esp-tools\tools\cmake\3.24.0\bin
D:\FC_ESP\esp-tools\tools\openocd-esp32\v0.12.0-esp32-20240318\openocd-esp32\bin
D:\FC_ESP\esp-tools\tools\ninja\1.11.1\
D:\FC_ESP\esp-tools\tools\idf-exe\1.0.3\
D:\FC_ESP\esp-tools\tools\ccache\4.8\ccache-4.8-windows-x86_64
D:\FC_ESP\esp-tools\tools\dfu-util\0.11\dfu-util-0.11-win64
D:\FC_ESP\frameworks\esp-idf-v5.3.1\tools

Checking if Python packages are up to date...
Python requirements are satisfied.
Constraint file: D:\FC_ESP\esp-tools\espidf.constraints.v5.3.txt
Requirement files:
- D:\FC_ESP\frameworks\esp-idf-v5.3.1\tools\requirements\requirements.core.txt
Python being checked: D:\FC_ESP\esp-tools\python_env\idf5.3_py3.11_env\Scripts\python.exe
.


Done! You can now compile ESP-IDF projects.
Go to the project directory and run:

idf.py build

Target: esp32c3 ...
-- Found Git: D:/FC_ESP/esp-tools/tools/idf-git/2.44.0/bin/git.exe (found version "2.44.0.windows.1")
-- git rev-parse returned 'fatal: not a git repository (or any of the parent directories): .git'
. .

fatal: not a git repository (or any of the parent directories): .git
-- ccache will be used for faster recompilation
-- The C compiler identification is unknown
. . . .

-- The CXX compiler identification is unknown
-- The ASM compiler identification is GNU
-- Found assembler: D:/FC_ESP/esp-tools/tools/riscv32-esp-elf/esp-13.2.0_20240530/riscv32-esp-elf/bin/riscv32-esp-elf-gcc.exe
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - failed
-- Check for working C compiler: D:/FC_ESP/esp-tools/tools/riscv32-esp-elf/esp-13.2.0_20240530/riscv32-esp-elf/bin/riscv32-esp-elf-gcc.exe
-- Check for working C compiler: D:/FC_ESP/esp-tools/tools/riscv32-esp-elf/esp-13.2.0_20240530/riscv32-esp-elf/bin/riscv32-esp-elf-gcc.exe - broken
CMake Error at D:/FC_ESP/esp-tools/tools/cmake/3.24.0/share/cmake-3.24/Modules/CMakeTestCCompiler.cmake:69 (message):
The C compiler
"D:/FC_ESP/esp-tools/tools/riscv32-esp-elf/esp-13.2.0_20240530/riscv32-esp-elf/bin/riscv32-esp-elf-gcc.exe"
is not able to compile a simple test program.
It fails with the following output:
Change Dir: D:/FC_ESP/mtxesp32_c3_sdkconfig/build/CMakeFiles/CMakeTmp

Run Build Command(s):D:/FC_ESP/esp-tools/tools/ninja/1.11.1/ninja.exe cmTC_cea33 && [1/2] Building C object CMakeFiles\cmTC_cea33.dir\testCCompiler.c.obj
FAILED: CMakeFiles/cmTC_cea33.dir/testCCompiler.c.obj
D:\FC_ESP\esp-tools\tools\riscv32-esp-elf\esp-13.2.0_20240530\riscv32-esp-elf\bin\riscv32-esp-elf-gcc.exe -march=rv32imc_zicsr_zifencei -o CMakeFiles\cmTC_cea33.dir\testCCompiler.c.obj -c D:\FC_ESP\mtxesp32_c3_sdkconfig\build\CMakeFiles\CMakeTmp\testCCompiler.c
Assembler messages:
Fatal error: invalid -march= option: `rv32imc_zicsr_zifencei'
ninja: build stopped: subcommand failed.



CMake will not be able to correctly generate this project.
Call Stack (most recent call first):
D:/FC_ESP/frameworks/esp-idf-v5.3.1/tools/cmake/project.cmake:564 (__project)
CMakeLists.txt:13 (project)
-- Configuring incomplete, errors occurred!
See also "D:/FC_ESP/mtxesp32_c3_sdkconfig/build/CMakeFiles/CMakeOutput.log".
See also "D:/FC_ESP/mtxesp32_c3_sdkconfig/build/CMakeFiles/CMakeError.log".
cmake failed with exit code 1
Executing action: all (aliases: build)
Running cmake in directory D:\FC_ESP\mtxesp32_c3_sdkconfig\build
Executing "cmake -G Ninja -DPYTHON_DEPS_CHECKED=1 -DPYTHON=D:\FC_ESP\esp-tools\python_env\idf5.3_py3.11_env\Scripts\python.exe -DESP_PLATFORM=1 -DIDF_TARGET=esp32c3 -DCCACHE_ENABLE=1 D:\FC_ESP\mtxesp32_c3_sdkconfig"...

Build Failed.

C:\ProgramData\MatrixTSL\FlowcodeV10\FCD\ESP\Batch\esp32_build.bat reported error code 0x1

Autoclose turned off


FINISHED

-----------------------


please have a look at it and let me know how to fix it.
Thanks!

Best regards,
Deqiang

jgu1
Posts: 811
Joined: Thu Dec 03, 2020 8:25 pm
Location: Denmark
Has thanked: 691 times
Been thanked: 183 times

Re: ESP32-C3 Compile to Target Failure

Post by jgu1 »

Hi Dequiang!

Please have a look here and go to almost the of the tread and see what Martin, medelec write.

Look like there are an issue with IDF 5.3

viewtopic.php?p=19870&hilit=jgu1+c3#p19870

Br Jorgen ;)

liudeqiang_2008
Posts: 52
Joined: Wed Jan 12, 2022 8:25 am
Has thanked: 10 times
Been thanked: 1 time

Flowcode v10 Re: ESP32-C3 Compile to Target Failure

Post by liudeqiang_2008 »

jgu1 wrote:
Fri Jul 25, 2025 6:20 am
Hi Dequiang!

Please have a look here and go to almost the of the tread and see what Martin, medelec write.

Look like there are an issue with IDF 5.3

viewtopic.php?p=19870&hilit=jgu1+c3#p19870

Br Jorgen ;)
Hi Jorgen,

Thank you for your fast reply.
I have checked the Espressif website, the lastest ESP-IDF version is v5.5, is it help to upgrade to v5.5 from v5.3.1 ?
If it may works, how to upgrade, just download the ESP-IDF Windows Installer and directly install it?


Or better move to ESP-S3 :roll:

Thanks
Br Deqiang
Attachments
屏幕截图 2025-07-25 144053.png
屏幕截图 2025-07-25 144053.png (55.86 KiB) Viewed 1201 times

jgu1
Posts: 811
Joined: Thu Dec 03, 2020 8:25 pm
Location: Denmark
Has thanked: 691 times
Been thanked: 183 times

Re: ESP32-C3 Compile to Target Failure

Post by jgu1 »

Hi again!

I don`t know if the 5.5 is better? I switched to the ESP32 S3 model. I also don`t know how to upgrade to 5.5 because my 5.3 was installed via ESP toolchain, but the S model work fine by me.

Nice weekend :D

Br Jorgen

liudeqiang_2008
Posts: 52
Joined: Wed Jan 12, 2022 8:25 am
Has thanked: 10 times
Been thanked: 1 time

Re: ESP32-C3 Compile to Target Failure

Post by liudeqiang_2008 »

jgu1 wrote:
Fri Jul 25, 2025 12:26 pm
Hi again!

I don`t know if the 5.5 is better? I switched to the ESP32 S3 model. I also don`t know how to upgrade to 5.5 because my 5.3 was installed via ESP toolchain, but the S model work fine by me.

Nice weekend :D

Br Jorgen
Agree!Better don't bother it
I have already ordered the new ESP32 S3 board today :D

Thanks and have a nice weekend!

Br Deqiang

celebriums
Posts: 45
Joined: Fri Dec 18, 2020 7:33 am
Location: Turkey
Has thanked: 23 times
Been thanked: 7 times
Contact:

Re: ESP32-C3 Compile to Target Failure

Post by celebriums »

Warm greetings to everyone from Istanbul. I hope you're all doing well.

Can someone please explain how we can change the ESP-IDF version to 5.1 or 5.5?

The current export.bat file is configured to call only version 5.3. It seems that Espressif has customized this setup specifically for the Flowcode ecosystem.

However, we need a tool or method that allows us to select different ESP-IDF versions, such as for the ESP32-C3 or other ESP32 series.

If someone can clearly explain how to do this, I’d be happy to apply and implement it for you.
Sadık Süme

mnfisher
Valued Contributor
Posts: 1627
Joined: Wed Dec 09, 2020 9:37 pm
Has thanked: 142 times
Been thanked: 758 times

Re: ESP32-C3 Compile to Target Failure

Post by mnfisher »

I posted a batch file at viewtopic.php?t=2966&hilit=esp32+batch that allows this....

I use this regularly - and it creates a new directory for each project (this allows me to use the espressif components such as lvgl or camera) The only issue is that the serial port is hard coded (I use COM6) but you might need to alter this - and I need to use compile to hex (not compile to target) - on the plus side I have 4 espressif frameworks installed and to swap I use the install.bat in the framework to choose between them....

Note that if you do switch version - you will need to do idf.py fullclean on the relevant project directory.

Martin

Post Reply