Booloader error

[dda_in_hk]

I bought a bunch of TTGO LoRa devices (https://www.aliexpress.com/item/2pcs-se ... 23252.html), and they work quite well. But one just started to act up, and is not working anymore. On reboot I get this error (among others):

Code: Select all

rst:0x1 (POWERON_RESET),boot:0x17 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0010,len:4
load:0x3fff0014,len:956
load:0x40078000,len:0
load:0x40078000,len:11856
entry 0x40078a34
user code done

Erasing the flash doesn't change anything. I uploaded a Blink.ino sketch, and after that check the flash state:

Code: Select all

/Users/dda/Documents/Arduino/hardware/espressif/esp32/tools/esptool --chip esp32 --port /dev/cu.SLAB_USBtoUART --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0xe000 /Users/dda/Documents/Arduino/hardware/espressif/esp32/tools/partitions/boot_app0.bin 0x1000 /Users/dda/Documents/Arduino/hardware/espressif/esp32/tools/sdk/bin/bootloader_qio.bin 0x10000 /var/folders/cd/dhg30ztj4cl0lt1l6g28wl480000gn/T/arduino_build_355485/Blink.ino.bin 0x8000 /var/folders/cd/dhg30ztj4cl0lt1l6g28wl480000gn/T/arduino_build_355485/Blink.ino.partitions.bin 

dda$ esptool --chip esp32 --port /dev/cu.SLAB_USBtoUART --baud 115200 --before default_reset --after hard_reset verify_flash 0x1000 /Users/dda/Documents/Arduino/hardware/espressif/esp32/tools/sdk/bin/bootloader_qio.bin
esptool.py v2.1
Connecting........__
Chip is ESP32D0WDQ6 (revision 1)
Uploading stub...
Running stub...
Stub running...
Configuring flash size...
Auto-detected Flash size: 16MB
Flash params set to 0x0240
Verifying 0x3270 (12912) bytes @ 0x00001000 in flash against /Users/dda/Documents/Arduino/hardware/espressif/esp32/tools/sdk/bin/bootloader_qio.bin...
-- verify FAILED (digest mismatch)

A fatal error occurred: Verify failed.

Other parts (boot_app0.bin, Blink.ino.bin, Blink.ino.partitions.bin) check out properly.

So I'm wondering what could have gone wrong, and whether there would be a way to bring back the device to life.

Thanks in advance.