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

wemos lolin32 Failed uploading: uploading error: exit status 2 (ESPTOOL-820) #961

Closed
Bri-iggy opened this issue Mar 3, 2024 · 2 comments

Comments

@Bri-iggy
Copy link

Bri-iggy commented Mar 3, 2024

Operating System

windows 11

Esptool Version

esptool.py v4.6

Python Version

Python 3.12.2

Full Esptool Command Line that Was Run

--chip esp32 --port "COM3" --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode keep --flash_freq keep --flash_size keep 0x1000

Esptool Output

--chip esp32 --port "COM3" --baud 115200  --before default_reset --after hard_reset write_flash  -z --flash_mode keep --flash_freq keep --flash_size keep 0x1000
esptool.py v4.6
Serial port COM3
Connecting......................................

A fatal error occurred: Failed to connect to ESP32: Wrong boot mode detected (0x13)! The chip needs to be in download mode.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/latest/troubleshooting.html
Failed uploading: uploading error: exit status 2

What is the Expected Behaviour?

It supposed to get the chip Id

More Information

I tried on my friend's pc and it has the same error

Other Steps to Reproduce

No response

@github-actions github-actions bot changed the title wemos lolin32 Failed uploading: uploading error: exit status 2 wemos lolin32 Failed uploading: uploading error: exit status 2 (ESPTOOL-820) Mar 3, 2024
@dobairoland
Copy link
Collaborator

The command is for writing flash instead of getting the chip id (chip_id). Also it is incomplete. After 0x1000 the binary should follow.

But not the above is causing the error. This is probably a hardware or OS driver issue. The troubleshooting guide is linked in the message. We probably couldn't suggest anything else.

@radimkarnis
Copy link
Collaborator

Closing this issue due to inactivity and incomplete information. Please go through the troubleshooting guide to see the recommended action.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants