When I'm flashing ESP32 Pico D4 on MacOs ARM 2/3 seconds after flash ends (after progress to 100%) it triggers
Flashing /Users/charles/Downloads/tasmota32-teleinfo-denkyd4.factory (5).bin: erase 0x00000000 - 0x007fffff...
[██████████████████████████████] 100% 0x0026a0ea
Flashing error: Error while writing flash: Serial data stream stopped: Possible serial noise or corruption.
Flashing failed!
I first suspected cable/baudrate, so I've done exactly same test, same device, same cable, same port with esptool and it did works at any baud rate (2000000, 1500000, 460800, ....)
esptool --port /dev/tty.usbserial-5B340413761 --baud 2000000 write_flash -z 0x0 ~/Downloads/tasmota32-teleinfo-denkyd4.fac.bin
Warning: Deprecated: Command 'write_flash' is deprecated. Use 'write-flash' instead.
esptool v5.2.0
Connected to ESP32 on /dev/tty.usbserial-5B340413761:
Chip type: ESP32-PICO-V3-02 (revision v3.1)
Features: Wi-Fi, BT, Dual Core + LP Core, 240MHz, Embedded Flash, Embedded PSRAM, Vref calibration in eFuse, Coding Scheme None
Crystal frequency: 40MHz
MAC: f4:2d:c9:05:3d:e4
Stub flasher running.
Changing baud rate to 2000000...
Changed.
Configuring flash size...
Flash will be erased from 0x00000000 to 0x007fffff...
Wrote 8388608 bytes (1628864 compressed) at 0x00000000 in 47.3 seconds (1418.7 kbit/s).
Hash of data verified.
Hard resetting via RTS pin...
The only thing I saw is timing, let me explain , after displaying (so when write was fully finished)
Writing at 0x00800000 [==============================] 100.0% 1628864/1628864 bytes...
it tooks 15/20 seconds then displayed
Wrote 8388608 bytes (1628864 compressed) at 0x00000000 in 47.5 seconds (1412.8 kbit/s).
Verifying written data...
waited again approx 6 seconds before displaying
Hash of data verified.
So may be timeout is too short on ESPFlasher after write and trigger error message, not sure what's going on out there, another user with same board encounter same issue, not sure if it's ESP32 Pico D4 related or OS but on my side works fine on command line (despite these 15/20 seconds wait)
When I'm flashing ESP32 Pico D4 on MacOs ARM 2/3 seconds after flash ends (after progress to 100%) it triggers
I first suspected cable/baudrate, so I've done exactly same test, same device, same cable, same port with esptool and it did works at any baud rate (2000000, 1500000, 460800, ....)
The only thing I saw is timing, let me explain , after displaying (so when write was fully finished)
Writing at 0x00800000 [==============================] 100.0% 1628864/1628864 bytes...it tooks 15/20 seconds then displayed
Wrote 8388608 bytes (1628864 compressed) at 0x00000000 in 47.5 seconds (1412.8 kbit/s).Verifying written data...waited again approx 6 seconds before displaying
Hash of data verified.So may be timeout is too short on ESPFlasher after write and trigger error message, not sure what's going on out there, another user with same board encounter same issue, not sure if it's ESP32 Pico D4 related or OS but on my side works fine on command line (despite these 15/20 seconds wait)