Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SystemExit Raised Instead of Warning in _check_if_can_reset Method when chip is placed into download mode using GPIO0 (ESPTOOL-893) #996

Closed
1 task done
DocKenny opened this issue Jul 18, 2024 · 0 comments

Comments

@DocKenny
Copy link

Operating System

Windows 10

Esptool Version

esptool-v4.7.0

Python Version

Python 3.11.7

Chip Description

ESP32S2 and ESP32S3

Device Description

ESP32-S2-WROOM
image

Hardware Configuration

No response

How is Esptool Run

Arduino IDE

Full Esptool Command Line that Was Run

No response

Esptool Output

Sketch uses 268886 bytes (20%) of program storage space. Maximum is 1310720 bytes.
Global variables use 14128 bytes (4%) of dynamic memory, leaving 313552 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.6
Serial port COM4
Connecting....
Chip is ESP32-S2 (revision v0.0)
Features: WiFi, No Embedded Flash, No Embedded PSRAM, ADC and temperature sensor calibration in BLK2 of efuse V2
Crystal is 40MHz
MAC: 70:04:1d:52:dc:dc
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00004fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x00051fff...
Compressed 15568 bytes to 11011...
Writing at 0x00001000... (16 %)
Writing at 0x00001c23... (33 %)
Writing at 0x00002767... (50 %)
Writing at 0x00003244... (66 %)
Writing at 0x00003ba6... (83 %)
Writing at 0x00004887... (100 %)
Wrote 15568 bytes (11011 compressed) at 0x00001000 in 0.5 seconds (effective 264.8 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 146...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (146 compressed) at 0x00008000 in 0.1 seconds (effective 215.1 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 519.6 kbit/s)...
Hash of data verified.
Compressed 269248 bytes to 153476...
Writing at 0x00010000... (1 %)
Writing at 0x00011136... (2 %)
Writing at 0x000129f6... (4 %)
Writing at 0x00013f5c... (5 %)
Writing at 0x00015a10... (6 %)
Writing at 0x0001720d... (8 %)
Writing at 0x000188f8... (9 %)
Writing at 0x0001a82f... (10 %)
Writing at 0x0001be79... (12 %)
Writing at 0x0001e51c... (13 %)
Writing at 0x000202cc... (14 %)
Writing at 0x00020f78... (16 %)
Writing at 0x00021a56... (17 %)
Writing at 0x0002245d... (18 %)
Writing at 0x00022e8c... (20 %)
Writing at 0x0002393c... (21 %)
Writing at 0x00024397... (22 %)
Writing at 0x00024f7c... (24 %)
Writing at 0x000259c5... (25 %)
Writing at 0x0002645d... (26 %)
Writing at 0x00026f1c... (28 %)
Writing at 0x0002798d... (29 %)
Writing at 0x00028380... (30 %)
Writing at 0x00028d69... (32 %)
Writing at 0x0002978a... (33 %)
Writing at 0x0002a1ff... (34 %)
Writing at 0x0002ae98... (36 %)
Writing at 0x0002b7a2... (37 %)
Writing at 0x0002c2e8... (38 %)
Writing at 0x0002cc88... (40 %)
Writing at 0x0002d65b... (41 %)
Writing at 0x0002e025... (42 %)
Writing at 0x0002eb3e... (44 %)
Writing at 0x0002f59e... (45 %)
Writing at 0x0002ffc2... (46 %)
Writing at 0x000309f8... (48 %)
Writing at 0x000313f4... (49 %)
Writing at 0x00031fc6... (50 %)
Writing at 0x00032975... (52 %)
Writing at 0x000332de... (53 %)
Writing at 0x00033dfb... (54 %)
Writing at 0x0003494d... (56 %)
Writing at 0x000354be... (57 %)
Writing at 0x00035f21... (58 %)
Writing at 0x000369b5... (60 %)
Writing at 0x00037601... (61 %)
Writing at 0x000388dd... (62 %)
Writing at 0x0003971c... (64 %)
Writing at 0x0003b8d4... (65 %)
Writing at 0x0003d42a... (66 %)
Writing at 0x0003ddd2... (68 %)
Writing at 0x0003e7aa... (69 %)
Writing at 0x0003f598... (70 %)
Writing at 0x00040a9c... (72 %)
Writing at 0x00042333... (73 %)
Writing at 0x00043bb7... (74 %)
Writing at 0x00044602... (76 %)
Writing at 0x000456b2... (77 %)
Writing at 0x000461af... (78 %)
Writing at 0x00046be1... (80 %)
Writing at 0x00047594... (81 %)
Writing at 0x00048058... (82 %)
Writing at 0x00048bf3... (84 %)
Writing at 0x00049769... (85 %)
Writing at 0x0004a2e3... (86 %)
Writing at 0x0004ac7b... (88 %)
Writing at 0x0004b6de... (89 %)
Writing at 0x0004c130... (90 %)
Writing at 0x0004cbe4... (92 %)
Writing at 0x0004d60f... (93 %)
Writing at 0x0004e0c8... (94 %)
Writing at 0x0004ee68... (96 %)
Writing at 0x0004fb78... (97 %)
Writing at 0x000504b5... (98 %)
Writing at 0x00050f86... (100 %)
Wrote 269248 bytes (153476 compressed) at 0x00010000 in 5.6 seconds (effective 384.7 kbit/s)...
Hash of data verified.

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

More Information

No response

Other Steps to Reproduce

No response

I Have Read the Troubleshooting Guide

  • I confirm I have read the troubleshooting guide.
@github-actions github-actions bot changed the title SystemExit Raised Instead of Warning in _check_if_can_reset Method when chip is placed into download mode using GPIO0 SystemExit Raised Instead of Warning in _check_if_can_reset Method when chip is placed into download mode using GPIO0 (ESPTOOL-893) Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant