Flowcode Support Board

Hi Team

I have just tryet to compile a program to ESP32 S2. I ger error1. As far I see it is something with the port. I see the programmerport in Project option and in devicemanager, but the Autodetect is Ghosted, again what am I do wrong, please.

Jorgen

Do you need to put into bootloader mode as with s3?

Press and hold boot and then press and release reset?

Martin

Hi Martin!

Thank’s I have already done this, othervice port22 is not comming up.

A fatal error occurred: Could not open COM_AUTODETECT, the port is busy or doesn't exist.
(could not open port 'COM_AUTODETECT':

Try removing the auto detect and setting the port manually?

Strange, It have programmed the device Martin, but why the error code It´s a vhile ago I used this device Martin, but now some bell is ringing, you have helped me with this challenge before, anyway I can program the device, again thank you for your fast reply and help

Configuring flash size...
Flash will be erased from 0x00001000 to 0x00006fff...
Flash will be erased from 0x00010000 to 0x00044fff...
Flash will be erased from 0x00008000 to 0x00008fff...
SHA digest in image updated
Compressed 22016 bytes to 13523...
Writing at 0x00001000... (14 %)
Writing at 0x00002555... (28 %)
Writing at 0x000031ee... (42 %)
Writing at 0x00003d8d... (57 %)
Writing at 0x000048a9... (71 %)
Writing at 0x0000529a... (85 %)
Writing at 0x00005e5e... (100 %)
Wrote 22016 bytes (13523 compressed) at 0x00001000 in 0.3 seconds (effective 611.4 kbit/s)...
Hash of data verified.
Compressed 213760 bytes to 110747...
Writing at 0x00010000... (1 %)
Writing at 0x000112a5... (3 %)
Writing at 0x00012cd4... (5 %)
Writing at 0x000144bf... (7 %)
Writing at 0x00015d38... (9 %)
Writing at 0x00017288... (10 %)
Writing at 0x00018be7... (12 %)
Writing at 0x0001a198... (14 %)
Writing at 0x0001c032... (16 %)
Writing at 0x0001ce54... (18 %)
Writing at 0x0001d85a... (20 %)
Writing at 0x0001e261... (21 %)
Writing at 0x0001eeb7... (23 %)
Writing at 0x0001fa40... (25 %)
Writing at 0x0002062d... (27 %)
Writing at 0x00021234... (29 %)
Writing at 0x00021d11... (30 %)
Writing at 0x000227e0... (32 %)
Writing at 0x00023250... (34 %)
Writing at 0x00024060... (36 %)
Writing at 0x00024ae7... (38 %)
Writing at 0x000255b6... (40 %)
Writing at 0x0002617c... (41 %)
Writing at 0x000270a4... (43 %)
Writing at 0x00027cb1... (45 %)
Writing at 0x0002879c... (47 %)
Writing at 0x00029267... (49 %)
Writing at 0x00029e5c... (50 %)
Writing at 0x0002a989... (52 %)
Writing at 0x0002b44d... (54 %)
Writing at 0x0002c06b... (56 %)
Writing at 0x0002cacb... (58 %)
Writing at 0x0002d62e... (60 %)
Writing at 0x0002e51f... (61 %)
Writing at 0x0002f803... (63 %)
Writing at 0x000322d3... (65 %)
Writing at 0x00033bf2... (67 %)
Writing at 0x0003537d... (69 %)
Writing at 0x00035eaf... (70 %)
Writing at 0x00036937... (72 %)
Writing at 0x00037984... (74 %)
Writing at 0x00039d12... (76 %)
Writing at 0x0003a79c... (78 %)
Writing at 0x0003b34e... (80 %)
Writing at 0x0003c0a9... (81 %)
Writing at 0x0003cc09... (83 %)
Writing at 0x0003d786... (85 %)
Writing at 0x0003e3b2... (87 %)
Writing at 0x0003f283... (89 %)
Writing at 0x0003fe32... (90 %)
Writing at 0x0004103e... (92 %)
Writing at 0x00041c16... (94 %)
Writing at 0x00042703... (96 %)
Writing at 0x00043323... (98 %)
Writing at 0x0004421b... (100 %)
Wrote 213760 bytes (110747 compressed) at 0x00010000 in 1.6 seconds (effective 1048.6 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.0 seconds (effective 771.5 kbit/s)...
Hash of data verified.

Leaving...
WARNING: ESP32-S2FNR2 (revision v0.0) chip was placed into download mode using GPIO0.
esptool.py can not exit the download mode over USB. To run the app, reset the chip manually.
To suppress this note, set --after option to 'no_reset'.
CMake Error at run_serial_tool.cmake:66 (message):

C:/FC_ESP_5.3/esp-tools/python_env/idf5.3_py3.11_env/Scripts/python.exe;;C:/FC_ESP_5.3/frameworks/esp-idf-v5.3.1/components/esptool_py/esptool/esptool.py;--chip;esp32s2
failed.
P_5.3/frameworks/esp-idf-v5.3.1/components/esptool_py/run_serial_tool.cmake"
FAILED: CMakeFiles/flash C:/FC_ESP_5.3/mtxesp32_s2_sdkconfig/build/CMakeFiles/flash
cmd.exe /C "cd /D C:\FC_ESP_5.3\frameworks\esp-idf-v5.3.1\components\esptool_py && C:\FC_ESP_5.3\esp-tools\tools\cmake\3.24.0\bin\cmake.exe -D IDF_PATH=C:/FC_ESP_5.3/frameworks/esp-idf-v5.3.1 -D SERIAL_TOOL=C:/FC_ESP_5.3/esp-tools/python_env/idf5.3_py3.11_env/Scripts/python.exe;;C:/FC_ESP_5.3/frameworks/esp-idf-v5.3.1/components/esptool_py/esptool/esptool.py;--chip;esp32s2 -D SERIAL_TOOL_ARGS=--before=default_reset;--after=hard_reset;write_flash;@flash_args -D WORKING_DIRECTORY=C:/FC_ESP_5.3/mtxesp32_s2_sdkconfig/build -P C:/FC_ESP_5.3/frameworks/esp-idf-v5.3.1/components/esptool_py/run_serial_tool.cmake"
ninja: build stopped: subcommand failed.
ninja failed with exit code 1
Executing action: flash
Running ninja in directory C:\FC_ESP_5.3\mtxesp32_s2_sdkconfig\build
Executing "ninja flash"...
Programming Failed.
.

C:\ProgramData\MatrixTSL\FlowcodeV11\FCD\ESP\Batch\esp32_prog.bat reported error code 0x1

Autoclose turned off

How did you sort it?

Hi Martin

Nothing

I suddenly recalled that I had encountered this exact issue before and asked about it here in the forum, where you previously replied: "It actually compiled."

Based on that, I gave it a few more tries and noticed that while compiling, the progress percentage counts all the way up, but it still ends with the error message. Naturally, it is a bit confusing and misleading when it states "Programming Failed" right at the end:

Programming Failed.

C:\ProgramData\MatrixTSL\FlowcodeV11\FCD\ESP\Batch\esp32_prog.bat reported error code 0x1

Autoclose turned off

FINISHED

Since that error is the very first thing you see after compilation, your immediate reaction is naturally that something went wrong.

Thanks again for your quick response, Martin!

Best regards

Jorgen

Hi Jorgen
Measure the voltage on GPIO0.
Even though it can be used for IO, don't load it as if IO0 is less then 0.8V it will be forced into download mode, which could be the error you are seeing.
What is the voltage of IO0?

I put together a list of ESP32 pins to use with caution.

Hi Martin,

My ESP32-S2 Mini board doesn't actually have a GPIO0 pin broken out on the pin headers—GPIO0 is only connected to the onboard BOOT button. Nothing external is connected to it, so it should remain pulled high during normal startup.