Stephen Rogers asked 2 years ago
Building in release mode
Retrieving maximum program size .pio\build\esp32doit-devkit-v1\firmware.elf
Checking size .pio\build\esp32doit-devkit-v1\firmware.elf
Advanced Memory Usage is available via “PlatformIO Home > Project Inspect”
RAM: [= ] 7.3% (used 23940 bytes from 327680 bytes)
Flash: [====== ] 55.7% (used 730594 bytes from 1310720 bytes)
I have a project assembled on a breadboard that uses the ESP32 DEVKIIT V1 DOIT. The basic hw design has been working for months, and I have been using it to develop C code for a datalogger product I’m building.
Suddenly, I have lost the ability to upload code. Here is what I get from the monitor:
Configuring upload protocol…
AVAILABLE: esp-prog, espota, esptool, iot-bus-jtag, jlink, minimodule, olimex-arm-usb-ocd, olimex-arm-usb-ocd-h, olimex-arm-usb-tiny-h, olimex-jtag-tiny, tumpa
CURRENT: upload_protocol = esptool
Looking for upload port…
Auto-detected: COM17
Uploading .pio\build\esp32doit-devkit-v1\firmware.bin
esptool.py v3.1
Serial port COM17
Connecting….
Chip is ESP32-D0WD (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 94:3c:c6:26:9d:88
Uploading stub…
Running stub…
Stub running…
Configuring flash size…
Warning: Could not auto-detect Flash size (FlashID=0xffffff, SizeID=0xff), defaulting to 4MB
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 0x000c2fff…
Compressed 17104 bytes to 11191…
A fatal error occurred: Timed out waiting for packet content
*** [upload] Error 2
========================================================================= [FAILED] Took 9.49 seconds
I have tried various things I found on rntlab and ESP32 forums. Nothing has worked. I did the electrolytic 10μF cap approach and shorting GPIO2 to ground and other ideas. Always get the above serial output.
Can you provide some insight? Again, this cropped after months of things working just fine. I always press the boot button when uploading.
Thanks, Stephen
Sara Santos Staff answered 2 years ago
Hi Stephen.
That error is a sign that your board is not in flashing mode.
It may be an issue with the board itself, some circuit is broken or something.
You may have peripherals connected to some specific GPIOs that prevent the board from going into flashing mode, the called “strapping pins”.
Do you have any peripherals connected to the board at the time of uploading?
Have you tried uploading code using Arduino IDE to check if it’s not an issue with VS Code?
Regards,
Sara
Stephen Rogers answered 2 years ago
I have just tried flashing the doit-devkit-v1 on a naked breadboard, no wires or devices on it. The one I’ve been using with the full circuit had the same upload issue. I then tried a different doit-devkit-v1 and it worked fine. So there is a difference between one of my doit-devkit-v1 boards and a different one. Damaged?
Next step will be to do another close review of the full board wiring and test it with the doit-devkit-v1 that uploads at least with no other circuitry attached.
Stephen Rogers answered 2 years ago
OK – I have ignition with a different doit-devkit-v1 on my circuit. I believe I must have fried the first doit-devkit-v1 somehow. I rechecked the circuit wiring and made sure the power is properly routed to the peripheral chips. So that is it for this thread unless you have a recommendation on how to test doit-devkit-v1.
Sara Santos Staff answered 2 years ago
Does the board light up the power LED when you provide power?
Did you try uploading a blank sketch to the board? Make sure the board is not connected to any peripherals, not even a breadboard, just to test it out.
Regards,
Sara