You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ESP32-S3 write_flash fails with 0105 checksum/invalid message error on v5.3.0, works fine on v4.8.1 (ESPTOOL-1363) #1178
Arduino IDE with esp32 core 3.3.10 (which calls the bundled esptool v5.3.0 via a new flasher.exe wrapper), and also reproduced by calling esptool.exe v5.3.0 directly from the command line, bypassing the wrapper.
esptool v5.3.0
Serial port COM6:
Connecting....
Connected to ESP32-S3 on COM6:
Chip type: ESP32-S3 (QFN56) (revision v0.2)
Features: Wi-Fi, BT 5 (LE), Dual Core + LP Core, 240MHz, Embedded PSRAM 8MB (AP_3v3)
Crystal frequency: 40MHz
MAC: 10:51:db:84:5b:ac
Uploading stub flasher...
A fatal error occurred: Failed to write to target RAM (result was 0107: Checksum error)
Failed uploading: uploading error: exit status 2
More Information
I systematically ruled out the following as causes (none changed the failure pattern):
3 different USB cables
Multiple USB ports (including different PCs)
USB-serial driver reinstall + Windows COM port latency timer setting
A Bluetooth SPP virtual COM port briefly sharing COM6 (confirmed not the same COM6 in use during failures)
Power delivery (different ports/machines)
Baud rate (115200, 460800, 9600)
Compression on/off (-z vs -u)
flash_id and other read-only ROM commands work correctly and return valid data every time — only write_flash operations fail.
Downgrading to esptool v4.8.1 and running the exact same command against the exact same binary files on the exact same hardware/port/cable completes successfully with no errors.
I suspect this may be related to the new default flasher stub (esp-flasher-stub) introduced in v5.3.0, the new USB VID:PID-based transport detection, or the improved flash chip connection verification (SFDP register check) — all changed in this release — but I haven't dug into the esptool source to pinpoint which.
Other Steps to Reproduce
Attempt to flash any application image (bootloader + partition table + boot_app0 + app binary) to this specific ESP32-S3 (revision v0.2) board using esptool v5.3.0. Full --trace logs are available if useful for debugging — happy to share on request.
Hi @vitorfr77! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.
Thank you for the detailed report — this is a well-documented issue. Here's what the knowledge sources can tell us, along with some recommended next steps.
What's Happening
The error Failed to write to target RAM (result was 0107: Checksum error) occurs during the stub flasher upload phase — before any actual flash writing begins. This is consistent with your observation that read-only ROM commands work fine but write_flash fails.
The knowledge sources confirm that esptool v5.3.0 introduced a significant change: [esptool v5.3.0]
This will confirm whether the new esp-flasher-stub is the root cause. [Flasher Stub]
2. Increase timeout values
The 0107: Checksum error during RAM write can sometimes be caused by unstable serial communication during larger data transfers (like uploading the stub). Try increasing timeouts via a configuration file — specifically the timeout and mem_end_rom_timeout values. [Troubleshooting]
3. Try a different USB-to-Serial adapter or eliminate USB hubs
Even though you've tried multiple cables and ports, the knowledge sources specifically recommend: [Troubleshooting]
Updating or changing USB-to-Serial drivers
Using a different USB-to-Serial adapter
Eliminating USB hubs and using a shorter, shielded cable
If a problem appears only with the default stub but disappears when falling back to the legacy stub, please report it in the esp-flasher-stub issue tracker so the new stub can be fixed before legacy support is removed.
Please share your --trace logs there — they will be very helpful for the maintainers to diagnose the issue with the new stub on ESP32-S3 revision v0.2.
changed the title [-]ESP32-S3 write_flash fails with 0105 checksum/invalid message error on v5.3.0, works fine on v4.8.1[/-][+]ESP32-S3 write_flash fails with 0105 checksum/invalid message error on v5.3.0, works fine on v4.8.1 (ESPTOOL-1363)[/+]on Jul 15, 2026
Thanks for the analysis! I've opened a report on the esp-flasher-stub tracker as suggested, with full details and reproduction steps: espressif/esp-flasher-stub#94
Leaving this issue open for now in case it's useful to keep tracking from the esptool side, but happy to have it closed/consolidated if maintainers prefer to keep discussion only on the flasher-stub repo.
Activity
github-actions commentedon Jul 15, 2026
Hi @vitorfr77! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.
Thank you for the detailed report — this is a well-documented issue. Here's what the knowledge sources can tell us, along with some recommended next steps.
What's Happening
The error
Failed to write to target RAM (result was 0107: Checksum error)occurs during the stub flasher upload phase — before any actual flash writing begins. This is consistent with your observation that read-only ROM commands work fine butwrite_flashfails.The knowledge sources confirm that esptool v5.3.0 introduced a significant change: [esptool v5.3.0]
This means the stub being uploaded to RAM in v5.3.0 is different from the one in v4.8.1, which aligns with your regression observation.
Recommended Workarounds to Try
1. Disable the stub loader (most direct test)
Run esptool with
--no-stubto bypass the new flasher stub entirely and use the ROM bootloader directly:This will confirm whether the new
esp-flasher-stubis the root cause. [Flasher Stub]2. Increase timeout values
The
0107: Checksum errorduring RAM write can sometimes be caused by unstable serial communication during larger data transfers (like uploading the stub). Try increasing timeouts via a configuration file — specifically thetimeoutandmem_end_rom_timeoutvalues. [Troubleshooting]3. Try a different USB-to-Serial adapter or eliminate USB hubs
Even though you've tried multiple cables and ports, the knowledge sources specifically recommend: [Troubleshooting]
Where to Report
Since the failure occurs inside the stub upload (stub behaviour), the appropriate place to report this is the esp-flasher-stub issue tracker: https://github.com/espressif/esp-flasher-stub/issues [Flasher Stub]
The knowledge sources specifically note:
Please share your
--tracelogs there — they will be very helpful for the maintainers to diagnose the issue with the new stub on ESP32-S3 revision v0.2.[-]ESP32-S3 write_flash fails with 0105 checksum/invalid message error on v5.3.0, works fine on v4.8.1[/-][+]ESP32-S3 write_flash fails with 0105 checksum/invalid message error on v5.3.0, works fine on v4.8.1 (ESPTOOL-1363)[/+]vitorfr77 commentedon Jul 15, 2026
Thanks for the analysis! I've opened a report on the esp-flasher-stub tracker as suggested, with full details and reproduction steps: espressif/esp-flasher-stub#94
Leaving this issue open for now in case it's useful to keep tracking from the esptool side, but happy to have it closed/consolidated if maintainers prefer to keep discussion only on the flasher-stub repo.