esptool.py v2.6
Serial port COM4
Connecting....
Chip is ESP8266EX
Features: WiFi
MAC: ec:fa:bc:85:8d:d0
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 4MB
Compressed 284160 bytes to 204357...
Writing at 0x00000000... (7 %)
Writing at 0x00004000... (15 %)
Writing at 0x00008000... (23 %)
Writing at 0x0000c000... (30 %)
Writing at 0x00010000... (38 %)
Writing at 0x00014000... (46 %)
Writing at 0x00018000... (53 %)
Writing at 0x0001c000... (61 %)
Writing at 0x00020000... (69 %)
Writing at 0x00024000... (76 %)
Writing at 0x00028000... (84 %)
Writing at 0x0002c000... (92 %)
Writing at 0x00030000... (100 %)
Wrote 284160 bytes (204357 compressed) at 0x00000000 in 18.1 seconds (effective 125.7 kbit/s)...
Hash of data verified.
...Writing at 0x0002c000... (92 %)
Writing at 0x00030000... (100 %)
Wrote 284160 bytes (204357 compressed) at 0x00000000 in 18.1 seconds (effective 125.7 kbit/s)...
Hash of data verified.
Leaving...
Hard resetting via RTS pin...
Seems like it uploads and restarts. No sign of delete in the transcript.... There is no mention of delete in your original question...?
Why do you think that something is being deleted?
The RESET makes sense.
Perhaps the code being uploaded is unchanged, so the appearance is the execution is unchanged. (deleted?)
Do you have any Serial.print you can use to verify what is running after the reset?
RTS in old times , means “ready to send” ( data) - this line changes when data is sent and changes back afterwards and is used to perform a hardware reset - really a restart of the program that is within memory .
it is supposed to do that.
Try loading up a simple example program to see if that works ok
Hey guys, can`t see the trees trough the forest.
Leaving...
Hard resetting via RTS pin...
it kills my patience
I just tried the solution from Pert but without any success
Open preferences.txt from C:\Users\AppData\Local\Arduino15 ( this path may vary depending on your
OS) and remove value for "boardsmanager.additional.urls"
Delete all .tmp files from this folder (C:\Users\AppData\Local\Arduino15)
Copy & paste URL in File->preferences
Goto Board-> Manager board... now you dont see any error and ESP8266 should be there in the list
Try adding on a print.serial to your code. I had the same problem and added this to the code to monitor via the Serial monitor and my project worked just fine.
Hope it helps
I encounter exactly the same problem.... Upload of the sketch (blink example) seems to work fine. But it ends with 'Hard resetting via RTS pin....'. Adding some Serial.print statements at the start of setup and loop functions does not show any output anywhere.
No clue what to try expect buy a new ESP 8266 and try again. Any suggestions? Did I wire the thing wrong?
I've been playing with a temperature sensor and wondered about the reset too. I could not get my sensor to display in the serial monitor and wondered if it was related to the reset. Strangest thing I changed my code from start the serial monitor to start the serial printer. I open the serial plotter and nothing then I try to open the serial monitor and get a message saying that you cannot open the monitor at the same time as the plotter. So I close the plotter and open the monitor and my program starts displaying my temperature in 5 second intervals. After all that I think that reset is just to restart the program. My 2 cents, weird about the printer, monitor, plotter though.
The hard reset thingy is, for the ESP32, normal operation. In fact, when you see that message things havewent well up to that point in loading the code onto your ESP32. If your coed does not work, then that another problem.
As a note, as had been stated already, the reset is to restart the ESP32 to begin using the new code uploaded. Your code is not being deleted from the ESP32.
The "Hard resetting via RTS pin..." is pretty much the same as "Rebooting after updates..."
One of the tutorials I was using had a different baud rate for Serial.begin(speed) then what was set in the serial monitor, so it seemed like nothing happens after it reboots. Which is the problem that led me to this thread. My advice is to make sure the baud rate is the same in the program as in the monitor. This can be selected via the bottom right drop-down selector in the monitor.
Several members have this issue.
Some responses are less than helpful.
"I guess al that means something to someone..."
"It doesn't happen to me..."
"It is normal for the ESP32..."
This worked for me. Tools > Reset Method > "no dtr (aka ck)".
Then I got this :
Writing at 0x00000000... (7 %)
Writing at 0x00004000... (15 %)
Writing at 0x00008000... (23 %)
Writing at 0x0000c000... (30 %)
Writing at 0x00010000... (38 %)
Writing at 0x00014000... (46 %)
Writing at 0x00018000... (53 %)
Writing at 0x0001c000... (61 %)
Writing at 0x00020000... (69 %)
Writing at 0x00024000... (76 %)
Writing at 0x00028000... (84 %)
Writing at 0x0002c000... (92 %)
Writing at 0x00030000... (100 %)
Wrote 277792 bytes (202445 compressed) at 0x00000000 in 18.0 seconds (effective 123.8 kbit/s)...
Hash of data verified.