ESP32 C3 Copiler error

Any bugs you encounter with Flowcode should be discussed here.
mnfisher
Valued Contributor
Posts: 1653
http://meble-kuchenne.info.pl
Joined: Wed Dec 09, 2020 9:37 pm
Has thanked: 142 times
Been thanked: 764 times

Re: ESP32 C3 Copiler error

Post by mnfisher »

Hi Sadik,

I've attempted a video (my hat is off to anyone who can work video editing (or indeed any graphics editing) software...

So - not very polished - I've clipped a few bits (download took ~20mins and install ~5mins). Uploading the video takes a wee while!

I actually chose the wrong target - esp32-c6 (instead of wroom-32) for the first compile - so upload failed. Setting the target right (save as new file or fullclean) put things to right.

Note - this uses my alternate batch file - as previously mentioned. So I do 'compile to hex' which compiles and uploads :-) The original batch files 'should' work - but if you want to change targets I think you will have issues.

https://youtu.be/zbGAvaV3hPE

Martin

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

Re: ESP32 C3 Copiler error

Post by mnfisher »

NB - it has captions....

celebriums
Posts: 51
Joined: Fri Dec 18, 2020 7:33 am
Location: Turkey
Has thanked: 25 times
Been thanked: 11 times
Contact:

Re: ESP32 C3 Copiler error

Post by celebriums »

Hello Dear Martin,
First of all, thank you very much for the video. It was a great start in your video, but I still made some mistakes.
I will explain the solutions to the mistakes and what I did in the next message.
Sadık Süme

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

Re: ESP32 C3 Copiler error

Post by mnfisher »

Thanks - i think folk are still having issues -although following the wiki instructions should be good😃

celebriums
Posts: 51
Joined: Fri Dec 18, 2020 7:33 am
Location: Turkey
Has thanked: 25 times
Been thanked: 11 times
Contact:

Re: ESP32 C3 Copiler error

Post by celebriums »

Flowcode 10 with ESP-IDF 5.5 – Installation and Error Fix

When using Flowcode with ESP-IDF, the old 5.3 packaged toolchain causes conflicts. The following steps describe how to switch to ESP-IDF 5.5 cleanly.

🔴 Important Point 1

Remove the pre-installed Flowcode toolchain (5.3) and delete everything inside C:\FC_ESP.
This package prevents us from updating to newer versions.

Step 1 – Download and Install ESP-IDF 5.5
______________________________________________________________________

Go to the ESP-IDF download page.
https://dl.espressif.com/dl/esp-idf/?idf=4.4

Download ESP-IDF v5.5 Offline Installer for Windows 10/11 (1.51 GB) or the latest stable version.

Select C:\FC_ESP as the installation directory (or create your own folder).

During installation:

Tick all checkboxes.

Select “Full install” to install all targets (recommended for Flowcode compatibility).

After installation, make sure you have desktop shortcuts for ESP-IDF 5.5 PowerShell and ESP-IDF 5.5 CMD.


Step 2 – Python
______________________________________________________________________

Install the latest stable version, currently Python 3.13.7 (64-bit).

Download: Python 3.13.7 (64-bit)
https://www.python.org/ftp/python/3.13. ... -amd64.exe


Step 3 – Git
______________________________________________________________________

Git is required. Current stable version: 2.51.0 (64-bit).

Download: Git-2.51.0-64-bit.exe
https://github.com/git-for-windows/git/ ... 64-bit.exe

Step 4 – Ninja and CMake Setup and ESP-IDF 5.5 activation
______________________________________________________________________

Navigate to C:\FC_ESP\frameworks\esp-idf-v5.5.

Run install.bat by double-clicking. This will fetch the required packages.
later
Run the following commands one by one. When finished, run the next command.


Then open the ESP-IDF 5.5 PowerShell shortcut on your desktop and run:

Code: Select all

PS C:\FC_ESP\frameworks\esp-idf-v5.5\tools> cd C:\FC_ESP\frameworks\esp-idf-v5.5
install.bat

Code: Select all

PS C:\FC_ESP\frameworks\esp-idf-v5.5> .\install.bat
export.bat

Code: Select all

PS C:\FC_ESP\frameworks\esp-idf-v5.5> .\export.bat
idf.py

Code: Select all

PS C:\FC_ESP\frameworks\esp-idf-v5.5> idf.py 
where idf.py

Code: Select all

PS C:\FC_ESP\frameworks\esp-idf-v5.5> where idf.py


Then open the ESP-IDF 5.5 PowerShell shortcut on your desktop and run:

Code: Select all

python idf_tools.py install

This installs and configures the required tools.
______________________________________________________________________

🔴 Important Point 2

If Flowcode doesn’t point to the correct ESP-IDF root, the compiler will fail.
Update the path inside Flowcode:

Flowcode → Build > Customize > Locations

Set ESP-IDF Root to:

C:\FC_ESP\frameworks\esp-idf-v5.5




Step 5 – Test in Flowcode
______________________________________________________________________

Create a new project → Select ESP32-C3 WROOM.

Save the file.

Click Compile to HEX.

The first build will take a while (up to ~1250 steps).

If successful, you will see a folder like this:

C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig


This indicates the toolchain is properly configured.

✅ Result

Flowcode now compiles using ESP-IDF v5.5 without errors.





Key takeaway: Point Flowcode to the correct ESP-IDF root folder and completely remove the old 5.3 package.

Notes:
Post title:
“Flowcode 10 – ESP-IDF 5.5 Installation (ESP32-C3 Example)”
Sadık Süme

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

Re: ESP32 C3 Copiler error

Post by mnfisher »

Sounds all good - glad someone else has it up and running - not just me :-)
I didn't install Python or GIT as I was upgrading - I've found installing both first (latest versions) also works well...

I've not had too many issues using 5.5 - though some warnings about deprecated components (timer / RMT)

Martin

celebriums
Posts: 51
Joined: Fri Dec 18, 2020 7:33 am
Location: Turkey
Has thanked: 25 times
Been thanked: 11 times
Contact:

Re: ESP32 C3 Copiler error (SOLVED)

Post by celebriums »

Hello Martin,
I got help from ChatGPT while solving this error. In my opinion, Flowcode should urgently integrate an AI module into its system for interpreting such errors. I don’t think this would be very difficult, because it can explain the subject almost like a teacher. A dedicated ChatGPT-like bot for Flowcode should be developed.
Otherwise, nobody can handle this many errors.

From the compiler messages below, what I understand is:

"Python 3.13.7
git version 2.51.0.windows.1
ESP toolchain found at "C:\FC_ESP\frameworks\esp-idf-v5.5" "

There is a linker program working between Flowcode and ESP-IDF, and there is no problem here.
I think the real issue occurs between ESP-IDF and Python (Git).

I want to ask you a question: Do you also see the memory and RAM usage status on your side?


Code: Select all

Target folder: C:\ElektronikProjeler\ESPtest
Source name:   C:\ElektronikProjeler\ESPtest\Flowcode2.fcfx
Title:         
Description:   
Device:        ESP.ESP32.ESP32-C3_WROOM
Generated by:  Flowcode v10.1.2.40
Date:          Monday, September 15, 2025 12:20:46
Users:         1
Registered to: mehmet64 (99154532)
Licence key: 9P152P
https://www.flowcode.co.uk
Using FCD settings for compiler
Launching the compiler...
C:\ProgramData\MatrixTSL\FlowcodeV10\FCD\ESP\Batch\esp32_build.bat  "C:\FC_ESP\frameworks\esp-idf-v5.5\" "Flowcode2" "C:\ElektronikProjeler\ESPtest\" esp32_c3_sdkconfig esp32c3

C:\ElektronikProjeler\ESPtest>REM CRC: 0796FC1E6A776AF9156B257209C35258CE7C28B3EC20AEA2C632DB392A0E4BFD5B3F53B21811978F7B21FE4085045A7E774D1D3D69D8A99EE7320EAE740A5DB60228F42835EF5B88138FDEE58A4EE9C3A4BAF1B34E38B68E0C3CAEE8E7DA6987B808018476405B65B199900461C78937B42DEF8219F63A24580137A2F6C8FDB7553324EFF791947E8AB6FFD612B81BAA97C798A8F1CFC189DE5D38517747C774AF2DD6F839BAECF83F7F994C7164CE77868F480396BDEF2F2C3050DA273BE4EE69F15C302679453617F9EA00A6A8712D05E485F25DB02304E4565E63FDA312627DD474674123A97D 

C:\ElektronikProjeler\ESPtest>REM REVISION: 15.0 

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

C:\ElektronikProjeler\ESPtest>REM DATE: 07\04\2025 

C:\ElektronikProjeler\ESPtest>REM DIR: FCD\ESP\Batch\esp32_build.bat 
.
============================== Toolchain Check ==============================
Python 3.13.7
git version 2.51.0.windows.1
ESP toolchain found at "C:\FC_ESP\frameworks\esp-idf-v5.5\"
=============================================================================
.
Building: Flowcode2 ...
IDF Version: v5.5 ...
Activating ESP-IDF 5.5
Setting IDF_PATH to 'C:\FC_ESP\frameworks\esp-idf-v5.5'.
* Checking python version ... 
3.13.7
* Checking python dependencies ... 
OK
* Deactivating the current ESP-IDF environment (if any) ... 
OK
* Establishing a new ESP-IDF environment ... 
. . . .

OK
* Identifying shell ... 
cmd.exe
* Detecting outdated tools in system ... 
Found tools that are not used by active ESP-IDF version.
For removing old versions of idf-driver, idf-python-wheels use command 'python.exe C:\FC_ESP\frameworks\esp-idf-v5.5\tools\idf_tools.py uninstall'
To free up even more space, remove installation packages of those tools.
Use option python.exe C:\FC_ESP\frameworks\esp-idf-v5.5\tools\idf_tools.py uninstall --remove-archives.

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

  idf.py build

Target: esp32c3 ...
[1/9] Performing build step for 'bootloader'
[1/1] C:\Windows\system32\cmd.exe /C "cd /D C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build\bootloader\esp-idf\esptool_py && C:\FC_ESP\python_env\idf5.5_py3.13_env\Scripts\python.exe C:/FC_ESP/frameworks/esp-idf-v5.5/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x0 C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/bootloader/bootloader.bin"
Bootloader binary size 0x5240 bytes. 0x2dc0 bytes (36%) free.
[2/9] No install step for 'bootloader'
[3/9] Completed 'bootloader'
.

[4/9] Building C object esp-idf/main/CMakeFiles/__idf_main.dir/esp-project.c.obj
[5/9] Linking C static library esp-idf\main\libmain.a
. . . . . .

[6/9] Generating esp-idf/esp_system/ld/sections.ld
[7/9] Linking CXX executable esp-project.elf
[8/9] Generating binary image from built executable
esptool.py v4.10.dev2
Creating esp32c3 image...
Merged 1 ELF section
Successfully created esp32c3 image.
Generated C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/esp-project.bin
[9/9] C:\Windows\system32\cmd.exe /C "cd /D C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build\esp-idf\esptool_py && C:\FC_ESP\python_env\idf5.5_py3.13_env\Scripts\python.exe C:/FC_ESP/frameworks/esp-idf-v5.5/components/partition_table/check_sizes.py --offset 0x8000 partition --type app C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/partition_table/partition-table.bin C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/esp-project.bin"
esp-project.bin binary size 0x35980 bytes. Smallest app partition is 0x100000 bytes. 0xca680 bytes (79%) free.
Executing action: all (aliases: build)
Running ninja in directory C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build
Executing "ninja all"...

Project build complete. To flash, run:
 idf.py flash
or
 idf.py -p PORT flash
or
 python -m esptool --chip esp32c3 -b 460800 --before default_reset --after hard_reset write_flash --flash_mode dio --flash_size 2MB --flash_freq 40m 0x0 build\bootloader\bootloader.bin 0x8000 build\partition_table\partition-table.bin 0x10000 build\esp-project.bin
or from the "C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build" directory
 python -m esptool --chip esp32c3 -b 460800 --before default_reset --after hard_reset write_flash "@flash_args"

Get Project Build Statistics
[1/4] C:\Windows\system32\cmd.exe /C "cd /D C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build\esp-idf\esptool_py && C:\FC_ESP\python_env\idf5.5_py3.13_env\Scripts\python.exe C:/FC_ESP/frameworks/esp-idf-v5.5/components/partition_table/check_sizes.py --offset 0x8000 partition --type app C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/partition_table/partition-table.bin C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/esp-project.bin"
esp-project.bin binary size 0x35980 bytes. Smallest app partition is 0x100000 bytes. 0xca680 bytes (79%) free.
[2/4] Performing build step for 'bootloader'
[1/1] C:\Windows\system32\cmd.exe /C "cd /D C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build\bootloader\esp-idf\esptool_py && C:\FC_ESP\python_env\idf5.5_py3.13_env\Scripts\python.exe C:/FC_ESP/frameworks/esp-idf-v5.5/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x0 C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/bootloader/bootloader.bin"
Bootloader binary size 0x5240 bytes. 0x2dc0 bytes (36%) free.
[3/4] No install step for 'bootloader'
[4/4] Completed 'bootloader'
[0/1] C:\Windows\system32\cmd.exe /C "cd /D C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build && C:\FC_ESP\tools\cmake\3.30.2\bin\cmake.exe -D IDF_SIZE_TOOL=C:/FC_ESP/python_env/idf5.5_py3.13_env/Scripts/python.exe;-m;esp_idf_size -D MAP_FILE=C:/FC_ESP/frameworks/esp-idf-v5.5/mtxesp32_c3_sdkconfig/build/esp-project.map -D OUTPUT_JSON= -P C:/FC_ESP/frameworks/esp-idf-v5.5/tools/cmake/run_size_tool.cmake"
.

                            Memory Type Usage Summary                             
+--------------------------------------------------------------------------------+
| Memory Type/Section | Used [bytes] | Used [%] | Remain [bytes] | Total [bytes] |
|---------------------+--------------+----------+----------------+---------------|
| Flash Code          |       119562 |          |                |               |
|    .text            |       119562 |          |                |               |
| DRAM                |        62502 |    19.45 |         258794 |        321296 |
|    .text            |        53002 |     16.5 |                |               |
|    .data            |         5676 |     1.77 |                |               |
|    .bss             |         3824 |     1.19 |                |               |
| Flash Data          |        41132 |          |                |               |
|    .rodata          |        40876 |          |                |               |
|    .appdesc         |          256 |          |                |               |
| RTC SLOW            |           56 |     0.68 |           8136 |          8192 |
|    .force_fast      |           32 |     0.39 |                |               |
|    .rtc_reserved    |           24 |     0.29 |                |               |
+--------------------------------------------------------------------------------+
Total image size: 219404 bytes (.bin may be padded larger)
Note: The reported total sizes may be smaller than those in the technical reference manual due to reserved memory and application configuration. The total flash size available for the application is not included by default, as it cannot be reliably determined due to the presence of other data like the bootloader, partition table, and application partition size.
Executing action: size
Running ninja in directory C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build
Executing "ninja all"...
Running ninja in directory C:\FC_ESP\frameworks\esp-idf-v5.5\mtxesp32_c3_sdkconfig\build
Executing "ninja size"...
Build completed successfully 

Using FCD settings for linker
Launching the linker/assembler...
C:\Program Files (x86)\Flowcode v10\tools\DoNothing\DoNothing.exe  


FINISHED
Sadık Süme

Post Reply