Problem with Chip ESP32-S2FNR2 v1.0

[en3k1x]

I bought an ESP32-S2 and it has an ESP32-S2FNR2 chip (revision v1.0) and it has all the drivers installed and it keeps giving me an error installing the firmware even after entering BOOTLOADER mode (holding the BOOT button, pressing RESET and then releasing BOOT) I have downloaded esptool.exe inside the corresponding folder and I have seen that there are different .bin files depending on the board, but I don't know if mine corresponds to any of those and I have done everything indicated in the corresponding article (https://help.rewasd.com/external-devices/esp32-s2.html) and it keeps giving me an error. It should be noted that it is ESP32-S2 mini and only has a USB-C port, I am waiting for a UART-USB A adapter, so I do not know if you have to connect from the USB that acts as UART or with the native that brings the board would work.

Thank you.

[strokel]

Hey there!

Please run reWASD as administrator, go to Preferences, select 'Standard logging', and make sure both checkboxes for 'Service/Driver logs' and 'GUI/Agent logs' are enabled. Then click 'Start log'.
After that, try flashing your ESP32-S2 again. Once you encounter the issue, go back to Preferences, stop the logging, and send the logs to us.

Please make sure to include the file named reWASDHardwarelog.txt.

[en3k1x]

Thank you very much for your reply, here is the resulting file:

19/06/2025 10:31:58 Try to open port COM3
19/06/2025 10:31:59 Try to init port COM3
19/06/2025 10:31:59 CheckForRewasdFirmwareVersion: port COM3
19/06/2025 10:31:59 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:00 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:01 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:01 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:02 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:03 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:04 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:05 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:05 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:06 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:32:07 CheckForRewasdFirmwareVersion: Current device has not Rewasd firmware.
19/06/2025 10:32:07 Try to close port COM3
19/06/2025 10:32:08 SetFirmwarePath: C:\Program Files\reWASD\\firmware\REWASD_ESP32_1_05.zip firmware for ESP32 file was chosen.
19/06/2025 10:32:08 SetFirmwarePath: C:\Program Files\reWASD\\firmware\REWASD_ESP32-S2_1_01.zip firmware for ESP32S2 file was chosen.
19/06/2025 10:32:08 StartEsptool: esptool COM3 port.
19/06/2025 10:32:08 StartEsptool: Arguments: --port COM3 --baud 500000 --chip esp32s2 --before default_reset --after hard_reset write_flash 0x1000 "C:\Users\auror\AppData\Local\Temp\rdbbfx4g.03 k\bo otloader.bin" 0x8000 "C:\Users\auror\AppData\Local\Temp\rdbbfx4g.03 k\pa rtition-table.bin" 0x10000 "C:\Users\auror\AppData\Local\Temp\rdbbfx4g.03 k\Re WASDBridge.bin" 0xF000 "C:\Users\auror\AppData\Local\Temp\rdbbfx4g.03 k\ge neric_bridge.bin"
19/06/2025 10:32:09 ExecTool: Write firmware process started.
19/06/2025 10:33:09 Error: TimeoutException: C:\ProgramData\Disc-Soft\reWASD\esptool\esptool.exe process did not return a response within 60 seconds.
19/06/2025 10:33:09 StartEsptool: Write firmware process finished with errors!
19/06/2025 10:33:09 Try to open port COM3
19/06/2025 10:33:09 Failed to open port COM3
19/06/2025 10:33:09 Try to close port COM3
19/06/2025 10:33:09 Try to close port COM3
19/06/2025 10:38:49 Try to open port COM3
19/06/2025 10:38:49 Try to init port COM3
19/06/2025 10:38:49 CheckForRewasdFirmwareVersion: port COM3
19/06/2025 10:38:50 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:50 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:51 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:52 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:53 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:54 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:54 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:55 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:56 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:57 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:38:57 CheckForRewasdFirmwareVersion: Current device has not Rewasd firmware.
19/06/2025 10:38:57 Try to close port COM3
19/06/2025 10:38:59 SetFirmwarePath: C:\Program Files\reWASD\\firmware\REWASD_ESP32_1_05.zip firmware for ESP32 file was chosen.
19/06/2025 10:38:59 SetFirmwarePath: C:\Program Files\reWASD\\firmware\REWASD_ESP32-S2_1_01.zip firmware for ESP32S2 file was chosen.
19/06/2025 10:38:59 StartEsptool: esptool COM3 port.
19/06/2025 10:38:59 StartEsptool: Arguments: --port COM3 --baud 500000 --chip esp32s2 --before default_reset --after hard_reset write_flash 0x1000 "C:\Users\auror\AppData\Local\Temp\xxcvpt5t.fo t\bo otloader.bin" 0x8000 "C:\Users\auror\AppData\Local\Temp\xxcvpt5t.fo t\pa rtition-table.bin" 0x10000 "C:\Users\auror\AppData\Local\Temp\xxcvpt5t.fo t\Re WASDBridge.bin" 0xF000 "C:\Users\auror\AppData\Local\Temp\xxcvpt5t.fo t\ge neric_bridge.bin"
19/06/2025 10:38:59 ExecTool: Write firmware process started.
19/06/2025 10:38:59 Error: An error occurred trying to start process 'C:\ProgramData\Disc-Soft\reWASD\esptool\esptool.exe' with working directory 'C:\WINDOWS\system32'. La operación solicitada requiere elevación.
19/06/2025 10:38:59 StartEsptool: Write firmware process finished with errors!
19/06/2025 10:38:59 Try to open port COM3
19/06/2025 10:38:59 Try to init port COM3
19/06/2025 10:38:59 CheckForRewasdFirmwareVersion: port COM3
19/06/2025 10:39:00 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:01 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:01 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:02 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:03 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:04 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:05 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:05 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:06 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:07 CheckForRewasdFirmwareVersion: ReadFile return 0
19/06/2025 10:39:08 CheckForRewasdFirmwareVersion: Current device has not Rewasd firmware.
19/06/2025 10:39:08 Try to close port COM3
19/06/2025 10:39:08 Try to close port COM3

[1ncorrect]

You need to try to manually flash the board via esptool.exe with the following launch parameters:
esptool.exe --port COM3 --baud 500000 --chip esp32s2 --before default_reset --after hard_reset write_flash 0x1000 "bootloader.bin" 0x8000 "partition-table.bin" 0x10000 "ReWASDBridge.bin" 0xF000 "generic_bridge.bin"

Important: before calling this command, you need to know the exact COM port number.

You need to drop the .bin files specified in the command into the folder with esptool.exe

The files themselves can be taken from the archive:
C:\Program Files\reWASD\firmware\REWASD_ESP32-S2_1_01.zip

[en3k1x]

Hi !
I have done it, but I get an error at the end.
esptool.py v4.8.1
Serial port COM3
Connecting...
Chip is ESP32-S2FNR2 (revision v1.0)
Features: WiFi, Embedded Flash 4MB, Embedded PSRAM 2MB, ADC and temperature sensor calibration in BLK2 of efuse V2
Crystal is 40MHz
MAC: d8:3b:da:c8:fd:b8
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 500000
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00003fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x00010000 to 0x00088fff...
Flash will be erased from 0x0000f000 to 0x0000ffff...
Compressed 11392 bytes to 8264...
Wrote 11392 bytes (8264 compressed) at 0x00001000 in 0.1 seconds (effective 649.6 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 101...
Wrote 3072 bytes (101 compressed) at 0x00008000 in 0.0 seconds (effective 666.5 kbit/s)...
Hash of data verified.
Compressed 493856 bytes to 367337...
Wrote 493856 bytes (367337 compressed) at 0x00010000 in 3.7 seconds (effective 1054.1 kbit/s)...
Hash of data verified.
Compressed 256 bytes to 51...
Wrote 256 bytes (51 compressed) at 0x0000f000 in 0.0 seconds (effective 58.4 kbit/s)...
Hash of data verified.

Leaving...
Error: ESP32-S2FNR2 (revision v1.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'.

[en3k1x]

Also, I have to add that I am new to development boards and I did not buy the USB UART adapter with the board, I am waiting for it to arrive, as my esp32-s2 mini only has a usb-c, and as far as I understand it does not act as a native UART, but I need an adapter. However, I wanted to know if I can flash with the native USB-c of my esp32-s2, since REWASD detects it perfectly, and as you can see in the code it seems to flash it well but it gives an error saying that it can't reboot itself, which I think is why rewasd gives error.

Finally I have another question, if I flash it manually, will rewasd detect it as an external device and let me configure it?

[1ncorrect]

After consulting with the developers, we realized that your board is simply not supported. You can see the supported and tested board models here.
It is also important that the board contains 2 USB ports: one for the host PC with reWASD and the second for the target.

However, we would be grateful if you provide a link to your specific board model.

[en3k1x]

Thank you for your response. I as I said before I am a novice, but I think if it could be compatible because when I flash it manually as you told me it does not give me error, only that the port I am using can not be reset by itself because it is not UART, so I'm waiting for the adapter to see if it works that way. However, I tried to buy the esp32-s2 that you suggest but none of the stores sell them anymore. Also, in the log file I sent you, the program detects it as a generic board, since it is not any model like Maia or Nano, so I really suppose it should work because in your article it said that any well configured one could work. So in conclusion, I think it could be because the native USB of my esp32-s2 is not UART. I give you the link to my exact model (without the adapter) : https://a.aliexpress.com/_Ev9JWkA

Thank you very much for your patience!

[1ncorrect]

At least from the image of the board it is clear that it has one USB-C port. On the board variants that we recommend and tested, there are two ports.

[en3k1x]

I know it only has one USB port, however, I am waiting for a UART-USB adapter to arrive, and I think with a UART port it should work. Although you really don't have any way to check if my board with that UART adapter would be compatible?
Thank you in advance

[1ncorrect]

Unfortunately, we do not have such an opportunity, so we will wait for your feedback upon arrival of the adapter.

[DevX]

Please make sure that your UART adapter is connected to UART0 port of ESP32-S2 - is it used by communication from reWASD: GPIO43 is TX pin and GPIO44 is RX pin.
Also GPIO0 is typically connected to DTR signal from PC and used for entering bootloader and flashing.
This is typical scheme used most ESP32 boards:
A USB dongle to control EN and GPIO0 directly from a UART DTR and RTS for hands-free automatic programming of ESP modules. No need to press switches. : r/esp32
At the same time native USB port of ESP32-S2 (GPIO19 and GPIO20) will be used to create virtual controller.
These are basically the only requirements for our firmware to work.

[en3k1x]

Thank you very much for the detailed reply.
When I get it I will ask you any questions I have about it. Also, I wanted to ask if it is really necessary to connect DTR and RTS to GPIO0 and EN respectively or just by entering bootloader mode manually the rewasd flash would not give error.
Thank you again.

[DevX]

These are purely for convenience - they are used by esptool.py to reset the chip and enter bootloader. More info here:
Boot Mode Selection - ESP32 - — esptool.py latest documentation
So if you managed to enter bootloader manually and let reWASD flash the firmware without error then I think it is optional.
Also it should be noted that sometimes reWASD may try to reset the board during operaton too, eg. if it hangs and does not reply.
But such situation may be rare and it is not critical, if you don't mind to press the RESET button manually.