ESP32 Devkit v1, Failed uploading: uploading error: exit status 2

Anthem
Posts: 3
Joined: Mon Apr 01, 2024 9:52 am

ESP32 Devkit v1, Failed uploading: uploading error: exit status 2

Postby Anthem » Mon Apr 01, 2024 10:31 am

I just recently got into the esp32 and im currently making a project

The first time I uploaded a code for said project it worked fine, but the next day the board was unable to upload leading to the error message
Failed uploading: uploading error: exit status 2

The full error mesage would be this

Sketch uses 260561 bytes (19%) of program storage space. Maximum is 1310720 bytes.
Global variables use 21344 bytes (6%) of dynamic memory, leaving 306336 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.5.1
Serial port COM9
Connecting......
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: e8:6b:ea:d4:e4:90
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
WARNING: Failed to communicate with the flash chip, read/write operations will fail. Try checking the chip connections or removing any other hardware connected to IOs.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00010000 to 0x0004ffff...
Compressed 17568 bytes to 12204...

A fatal error occurred: Packet content transfer stopped (received 8 bytes)
Failed uploading: uploading error: exit status 2

But at some point i have gotten this error message

Sketch uses 260561 bytes (19%) of program storage space. Maximum is 1310720 bytes.
Global variables use 21344 bytes (6%) of dynamic memory, leaving 306336 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.5.1
Serial port COM9
Connecting......
Chip is ESP32-D0WD-V3 (revision v3.1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: e8:6b:ea:d4:e4:90
Uploading stub...

A fatal error occurred: Serial data stream stopped: Possible serial noise or corruption.
Failed uploading: uploading error: exit status 2

the code was a tester code in this instance which would make the ESP32 say hello world in the serial monitor

When I looked up the meaning of exit status 2 it said about having to do with the connection between the board and the computer and i tried some solutions such as pressing the boot button while its uploading and tried pressing both the boot and EN button but to no result, i have also tried switching my cables and the same results. As of now I haven't tried using a different computer.

I am currently using Windows 10, Arduino IDE version 2.3.2 and a driver "CP210x". Also when I plug the board windows tells me that im connected and the arduino aslo recognise that its connected so I am confused what the problem might be

If it was relevant the first time i used it just after finishing i tried pugging in a 9v battery to the breadboard that I had the ESP32 on.

lbernstone
Posts: 826
Joined: Mon Jul 22, 2019 3:20 pm

Re: ESP32 Devkit v1, Failed uploading: uploading error: exit status 2

Postby lbernstone » Tue Apr 02, 2024 5:26 pm

The most likely cause of this is a bad USB cable/port. Try a different port with the highest quality cable you have.
That said, applying 9V may very well have damaged the flash without injuring the cpu. This could appear to the esp32 like a communication failure.

Anthem
Posts: 3
Joined: Mon Apr 01, 2024 9:52 am

Re: ESP32 Devkit v1, Failed uploading: uploading error: exit status 2

Postby Anthem » Wed Apr 03, 2024 1:27 pm

I have tried switching cables and even changed computers just to confirm its not my computer port, so its likely the second answer. If so is there a way to fix it or am i forced to buy a new one?

ESP_Sprite
Posts: 9708
Joined: Thu Nov 26, 2015 4:08 am

Re: ESP32 Devkit v1, Failed uploading: uploading error: exit status 2

Postby ESP_Sprite » Thu Apr 04, 2024 2:45 am

You could try desoldering the flash and replacing it with a new one, but considering the time cost of that and that there may be other failures as well, I'd just grab a new devkit.

Who is online

Users browsing this forum: No registered users and 60 guests