ESP32-S2 presents false error message when set up without the 1200bps reset

[thorrak]

When doing the initial installation of firmware on an ESP32-S2 that hasn't previously been flashed, the 1200 bps reset doesn't work requiring the user to hold down the "0" button while pressing "reset". Once this is complete, an error message is raised since the chip cannot be automatically reset to exit flash mode, but BrewFlasher interprets this as a failed flash.

Sample log is as follows:

Verifying firmware list is up-to-date before downloading...
Downloading firmware...
Downloading partitions file...
Downloading SPIFFS/LittleFS file...
Downloading bootloader file...
Downloading otadata file...
Downloading main firmware file...
Downloaded successfully!

Performing 1200 bps touch
...done

Command: esptool.py --port /dev/cu.usbmodem01 --chip esp32s2 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m 0x10000 /private/var/folders/_2/8s8y9m_j3gb419d4ynb0h6p80000gn/T/firmware.bin 0x8000 /private/var/folders/_2/8s8y9m_j3gb419d4ynb0h6p80000gn/T/partitions.bin 0x1000 /private/var/folders/_2/8s8y9m_j3gb419d4ynb0h6p80000gn/T/bootloader.bin 0x330000 /private/var/folders/_2/8s8y9m_j3gb419d4ynb0h6p80000gn/T/spiffs.bin 0xe000 /private/var/folders/_2/8s8y9m_j3gb419d4ynb0h6p80000gn/T/otadata.bin --erase-all -fs detect

esptool.py v4.1
Serial port /dev/cu.usbmodem01
Connecting....
Chip is ESP32-S2FNR2
Features: WiFi, Embedded Flash 4MB, Embedded PSRAM 2MB, ADC and temperature sensor calibration in BLK2 of efuse V1
Crystal is 40MHz
MAC: 84:f7:03:f5:16:96
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Erasing flash (this may take a while)...
Chip erase completed successfully in 16.5s
Compressed 946352 bytes to 601011...
Writing at 0x00010000... (0 %)
Writing at 0x00010e7b... (0 %)
...
Writing at 0x000f5f55... (99 %)
Writing at 0x000f6af7... (100 %)
Wrote 946352 bytes (601011 compressed) at 0x00010000 in 10.8 seconds (effective 703.4 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 129...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (129 compressed) at 0x00008000 in 0.0 seconds (effective 595.0 kbit/s)...
Hash of data verified.
Compressed 13440 bytes to 9428...
Writing at 0x00001000... (20 %)
Writing at 0x00001c1c... (40 %)
Writing at 0x0000277a... (60 %)
Writing at 0x0000318b... (80 %)
Writing at 0x00003d5d... (100 %)
Wrote 13440 bytes (9428 compressed) at 0x00001000 in 0.2 seconds (effective 522.8 kbit/s)...
Hash of data verified.
Compressed 851968 bytes to 1760...
Writing at 0x00330000... (100 %)
Wrote 851968 bytes (1760 compressed) at 0x00330000 in 5.4 seconds (effective 1268.7 kbit/s)...
Hash of data verified.
Compressed 8192 bytes to 47...
Writing at 0x0000e000... (100 %)
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 806.4 kbit/s)...
Hash of data verified.

Leaving...
WARNING: ESP32-S2FNR2 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'.
Firmware flashing FAILED. esptool.py raised an error.

Try flashing again, or try flashing with a slower speed.


Alternatively, you may need to manually set the device into 'flash' mode.
For instructions on how to do this, check this website:
http://www.brewflasher.com/manualflash/

Key message to note is WARNING: ESP32-S2FNR2 chip was placed into download mode using GPIO0.. I don't think that we can capture this specific error coming out of esptool (though we should check) so the solution here may be to add a note about this in the message that we present about the firmware flashing failing.