ESP32 S2-Mini boards not working after uploading a sketch

pakorn4842
Posts: 1
Joined: Tue Apr 30, 2024 9:31 am

ESP32 S2-Mini boards not working after uploading a sketch

Postby pakorn4842 » Tue Apr 30, 2024 9:36 am

today is 30/04/2024
This problem has been searched for answers on Google.
No one has solved the problem yet.
----------------------------------------------------
the board is now recognized as COM4, and auto detected as "Deneyap Mini".
i set arduino-ide for the option( core debug level: verbose).
When I try to upload any sketch now, it almost completes before it always gives the following error:
------------------------------------------------------------------------------------
Sketch uses 305354 bytes (23%) of program storage space. Maximum is 1310720 bytes.
Global variables use 22304 bytes (6%) of dynamic memory, leaving 305376 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.6
Serial port COM4
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: cc:8d:a2:80:29:de
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Erasing flash (this may take a while)...
Chip erase completed successfully in 14.3s
Compressed 15552 bytes to 11005...
Writing at 0x00001000... (16 %)
Writing at 0x00001c24... (33 %)
Writing at 0x00002769... (50 %)
Writing at 0x00003244... (66 %)
Writing at 0x00003ba3... (83 %)
Writing at 0x00004883... (100 %)
Wrote 15552 bytes (11005 compressed) at 0x00001000 in 0.2 seconds (effective 673.9 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 146...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (146 compressed) at 0x00008000 in 0.0 seconds (effective 666.5 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 847.4 kbit/s)...
Hash of data verified.
Compressed 305712 bytes to 178489...
Writing at 0x00010000... (1 %)
Writing at 0x00011634... (2 %)
Writing at 0x00012cc8... (3 %)
Writing at 0x000143f5... (4 %)
Writing at 0x00015a32... (5 %)
Writing at 0x00017433... (6 %)
Writing at 0x00018fcc... (7 %)
Writing at 0x0001a288... (9 %)
Writing at 0x0001b904... (10 %)
Writing at 0x0001d6e5... (11 %)
Writing at 0x0001fbf5... (12 %)
Writing at 0x00020c24... (13 %)
Writing at 0x00021770... (14 %)
Writing at 0x000221b6... (15 %)
Writing at 0x00022cd6... (17 %)
Writing at 0x00023757... (18 %)
Writing at 0x0002420d... (19 %)
Writing at 0x00024c1f... (20 %)
Writing at 0x000256e9... (21 %)
Writing at 0x00026294... (22 %)
Writing at 0x00026c6a... (23 %)
Writing at 0x000277e1... (25 %)
Writing at 0x000282f2... (26 %)
Writing at 0x00028c9a... (27 %)
Writing at 0x000296af... (28 %)
Writing at 0x0002a092... (29 %)
Writing at 0x0002aaa9... (30 %)
Writing at 0x0002b595... (31 %)
Writing at 0x0002bf6a... (32 %)
Writing at 0x0002c8ff... (34 %)
Writing at 0x0002d35f... (35 %)
Writing at 0x0002dd72... (36 %)
Writing at 0x0002e738... (37 %)
Writing at 0x0002f1a9... (38 %)
Writing at 0x0002fcbd... (39 %)
Writing at 0x0003089b... (40 %)
Writing at 0x00031285... (42 %)
Writing at 0x00031c6f... (43 %)
Writing at 0x000326f8... (44 %)
Writing at 0x0003311a... (45 %)
Writing at 0x00033c1c... (46 %)
Writing at 0x0003464a... (47 %)
Writing at 0x00035101... (48 %)
Writing at 0x00035ac8... (50 %)
Writing at 0x000364b3... (51 %)
Writing at 0x00036f49... (52 %)
Writing at 0x00037b30... (53 %)
Writing at 0x000386b6... (54 %)
Writing at 0x0003901c... (55 %)
Writing at 0x00039adb... (56 %)
Writing at 0x0003a48d... (57 %)
Writing at 0x0003afef... (59 %)
Writing at 0x0003bc0d... (60 %)
Writing at 0x0003ccbc... (61 %)
Writing at 0x0003dd29... (62 %)
Writing at 0x0003e97c... (63 %)
Writing at 0x0003f7dd... (64 %)
Writing at 0x00040575... (65 %)
Writing at 0x00042fba... (67 %)
Writing at 0x00044165... (68 %)
Writing at 0x00044b3e... (69 %)
Writing at 0x000454c5... (70 %)
Writing at 0x00045e5b... (71 %)
Writing at 0x00046d62... (72 %)
Writing at 0x00048216... (73 %)
Writing at 0x00048d71... (75 %)
Writing at 0x00049acd... (76 %)
Writing at 0x0004a7fa... (77 %)
Writing at 0x0004cbd2... (78 %)
Writing at 0x0004d88a... (79 %)
Writing at 0x0004e290... (80 %)
Writing at 0x0004ee8b... (81 %)
Writing at 0x0005010f... (82 %)
Writing at 0x00050c90... (84 %)
Writing at 0x0005162c... (85 %)
Writing at 0x0005210b... (86 %)
Writing at 0x00052c1b... (87 %)
Writing at 0x00053701... (88 %)
Writing at 0x0005427b... (89 %)
Writing at 0x00054c92... (90 %)
Writing at 0x0005578c... (92 %)
Writing at 0x000562c8... (93 %)
Writing at 0x00056d42... (94 %)
Writing at 0x00057a05... (95 %)
Writing at 0x0005883c... (96 %)
Writing at 0x000591a1... (97 %)
Writing at 0x00059b9b... (98 %)
Writing at 0x0005a894... (100 %)
Wrote 305712 bytes (178489 compressed) at 0x00010000 in 2.3 seconds (effective 1074.1 kbit/s)...
Hash of data verified.

Leaving...
WARNING: 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'.
Failed uploading: uploading error: exit status 1

-------------------------------
Thank for your help.

MicroController
Posts: 1701
Joined: Mon Oct 17, 2022 7:38 pm
Location: Europe, Germany

Re: ESP32 S2-Mini boards not working after uploading a sketch

Postby MicroController » Wed May 01, 2024 1:28 pm

1) What kind of board are you using?
2) How do you get into download mode? Is there a ("BOOT") button on the board you press?
3) Do you have anything connected to the GPIO0 pin?

Who is online

Users browsing this forum: Google [Bot] and 105 guests