Use this forum to chat about hardware specific topics for the ESP8266 (peripherals, memory, clocks, JTAG, programming)

User avatar
By thompote
#90332 Hi everybody,

I already used different sketches on my lolin esp8266 D1 mini pro when suddenly it has become impossible.

Environment : I have same essor message using IDE or Arduino Create web app, before and after fully reinstall. Board is detected on /dev port but impossible to upload. I tried to change data cable.

You can see the error message

Is the board bricked ?

Any idea ?

Thanks everybody

Code: Select all[...]
runtime.tools.serial-discovery.path=/home/builder/.arduino15/packages/builtin/tools/serial-discovery/1.1.0 -libraries /tmp/533186290/custom -libraries /tmp/533186290/pinned /tmp/533186290/Blink

Sketch uses 258580 bytes (24%) of program storage space. Maximum is 1044464 bytes.

Global variables use 26696 bytes (32%) of dynamic memory, leaving 55224 bytes for local variables. Maximum is 81920 bytes.

Upload started

Programming with: Serial

Flashing with command:/Users/thomas/.arduino-create/esp8266/esptool/2.5.0-3-20ed2b9/esptool -vv -cd nodemcu -cb 921600 -cp /dev/cu.usbserial-1420 -ca 0x00000 -cf /var/folders/8t/bfs2gtl52wj78bxgtl5f51pm0000gn/T/arduino-create-agent394983170/Blink.bin

esptool v0.4.13-1-gf80ae31 - (c) 2014 Ch. Klippel <ck@atelier-klippel.de>

setting board to nodemcu

setting baudrate from 115200 to 921600

setting port from /dev/tty.usbserial to /dev/cu.usbserial-1420

setting address from 0x00000000 to 0x00000000

espcomm_upload_file

espcomm_upload_mem

opening port /dev/cu.usbserial-1420 at 921600

tcgetattr

warning: serialport_set_baudrate: baud rate 921600 may not work

tcsetattr

serial open

opening bootloader

resetting board

trying to connect

espcomm_send_command: sending command header

espcomm_send_command: sending command payload

trying to connect

espcomm_send_command: sending command header

espcomm_send_command: sending command payload

espcomm_send_command: receiving 2 bytes of data

espcomm_send_command: receiving 2 bytes of data

espcomm_send_command: receiving 2 bytes of data

espcomm_send_command: receiving 2 bytes of data

espcomm_send_command: receiving 2 bytes of data

espcomm_send_command: receiving 2 bytes of data

espcomm_send_command: receiving 2 bytes of data

espcomm_send_command: receiving 2 bytes of data

Uploading 262720 bytes from /var/folders/8t/bfs2gtl52wj78bxgtl5f51pm0000gn/T/arduino-create-agent394983170/Blink.bin to flash at 0x00000000

erasing flash

size: 040240 address: 000000

first_sector_index: 0

total_sector_count: 65

head_sector_count: 16

adjusted_sector_count: 49

erase_size: 031000

espcomm_send_command: sending command header

espcomm_send_command: sending command payload

setting timeout 15000

setting timeout 1000

warning: espcomm_send_command: didn't receive command response

warning: espcomm_send_command(FLASH_DOWNLOAD_BEGIN) failed

closing bootloader

error: espcomm_upload_mem failed
User avatar
By QuickFix
#90349 It doesn't have to be bricked, but nothing is impossible (especially with development boards you use a lot in testing/reflashing).

You could try to set the flash mode of your board manually instead of automatically:
  • Press and hold "Flash" button
  • Press and release "Reset" button
  • Release "Flash" button
  • Press play on tape (ie. start the flasher program)
Another possibility, I had the other day: I made an error in my code (was using the wrong GPIO's), resulting in my ESP constantly restarting (very quickly) which resulted in a "Dead" dev board (or USB -> serial bridge) not responding to the flash/reset signals anymore.

I was able to revive it again using the manual flash procedure above.