Help: A fatal error occurred: No serial data received.

gleiden

Hi - I'm new around here, so hello everryone.

I have been getting this error every few times I try to upload and must reconnect the Cardputer (disconnect, press G0 etc.) to get it working again. It happens maybe every 3rd time I want to upload and not only is it becoming very tedious, but I'm worried that it's eventually going to wear out the USB socket.

Does anyone know the solution to this and/or why this happens? I'm using Mac, Arduino IDE 2.3.3. All my libraries are up to date. As I said, it works 2/3 of the time then this happens.

Tried to search - there was a similar query but nobody answered it.

**Sketch uses 666477 bytes (50%) of program storage space. Maximum is 1310720 bytes.
Global variables use 92928 bytes (28%) of dynamic memory, leaving 234752 bytes for local variables. Maximum is 327680 bytes.
esptool.py v4.6
Serial port /dev/cu.usbmodem1101
Connecting...
Chip is ESP32-S3 (revision v0.2)
Features: WiFi, BLE
Crystal is 40MHz
MAC: 48:ca:43:39:2e:60
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600

A fatal error occurred: No serial data received.**

kuriko

@gleiden
Generally, No serial data received is because the ESP32 has not entered download mode successfully.

tmart11

@kuriko what is the way to fix this?

kuriko

@tmart11
enter download mode as mentioned in device document!

TomKatt

@gleiden
I know this is an old thread, but I just encountered this issue myself tonight. I believe the error is caused by the COM port being either unavailable or busy. In my case, I accidentally created a serial print function for debugging that was writing non-stop to the COM port - this was basically overloading the programmer's ability to get it's data through to begin uploading the new code. I got lucky because my code had a several second initiation routine before it started sending debug data to the COM port - so I unplugged the controller while the compiler was working and plugged in the usb cable just before the compiler was about to upload the code. This allowed the programmer to 'get through' the COM port before the code running on the controller started overwhelming the port.

There must be another way to solve this - I am surprised that pressing the button as you power on the controller to put it into download mode does not work... I would think that is the answer.

At least you know the reasoning for the error.