A fatal error occurred: Failed to write to target RAM (result was 0107) (ESPTOOL-95) #280

emeyedeejay · 2018-03-02T05:50:47Z

(Please delete any lines which don't apply.)

Operating system: Windows 10
Python version: 3.64
ESP hardware in use: ESP8266 on Itead SonOff smart WiFi switch (basic)
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi

Full esptool.py command line as run: python esptool.py --port COM3 read_flash 0x00000 0x100000 image1M.bin

Full output from esptool.py (please copy and paste all lines of output) D:\Downloads\esptool-2.3.1>python esptool.py --port COM3 read_flash 0x00000 0x100000 image1M.bin

esptool.py v2.3.1
Connecting....
Detecting chip type... ESP8266
Chip is ESP8266EX
Features: WiFi
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 0107)

What is the expected behaviour? Backup of current firmware

Do you have any other information from investigating this? Tried with 2 different USB -> Serial devices. FTDI232 and PROLIFIC USB-to-serail adapter

Is there any other information you can think of which will help us reproduce this problem?

projectgus · 2018-03-13T00:27:13Z

Hi @emeyedeejay,

Thanks for reporting this. The device is suddenly failing while uploading the "stub loader" code into its IRAM. Usually this suggests a power supply problem or a signal integrity problem with the USB/serial connections.

Check all power and signal/ground connections to the device. You could try setting a lower baud rate (for example -b 9600) and see if the problem improves at all.

Angus

emeyedeejay · 2018-03-13T07:42:18Z

Many thanks for the feedback/input.

I tried another actual FTDI USB->serial cable and was successful so it looks like it was my Chinese "ftdi" and USB-> serial components that are causing the issue here. It; odd though, they have never given me any issues with anything else I have ever used them for (Arduino based activity).

I'll try again with these devices to confirm them as the problem but it looks like you can close this issue.

If there is any additional info you want form me, please let me know...

Best,
Mike

projectgus · 2018-03-13T22:27:11Z

Thanks for the update. Feel free to reopen if you think there's something esptool should be doing differently here.

vgonet · 2018-08-29T12:11:23Z

Hello,

I've the same problem than emeyedeejay. I'm trying to program the ESP32 through a STM32. I convert the USB frames to USART (and USART to USB). The information sent by the ESP32 are OK until the Uploading stub. Do you know what is the problem ?

Thank you
Best
Vincent

Flashing binaries to serial port COM14 (app at offset 0x10000 )...
esptool.py v2.5.0
Serial port COM14
Connecting.....
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core
MAC: xx:xx:xx:xx:xx:xx
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 01050000)
make: *** [/home/Vincent/esp/esp-idf/components/esptool_py/Makefile.projbuild:63: flash] Error 2

stigok · 2018-10-21T20:17:24Z

FWIW: If using esptool on a Raspberry Pi using the GPIO serial interface at /dev/serial0 you have to disable the login shell being available on that device. You can disable this in the interface options in raspi-config.

This produced some different errors throughout 50 attempts, amongst them, the A fatal error occurred: Failed to write to target RAM (result was 0107), or a waiting for header timeout.

sandikodev · 2020-01-30T11:43:57Z

done with turn another plug usb

tneish · 2020-04-12T15:37:16Z

If you're flashing e.g. a sonoff make sure the "OTA" jumper is on/pin is bridged. Without it I think you get 0107 because the flash is write protected.

alunomakerdigital · 2020-12-08T18:21:30Z

Boa Tarde.
Estava com esse problema e foi RESOLVIDO COM AS ORIENTAÇÕES DESTE TÓPICO.
TROQUEI O CABO USB ...
PARABÉNS A TODOS.
MUITO GRATO.

azrin1972 · 2021-05-23T10:44:35Z

Hi,

Im using a LilyGo TTGO T-Call Sim800L v1.4

The upload UART is using the USB C. here is the error I'm getting

lordofswe · 2021-05-27T11:35:47Z

I am using another LilyGo product but the same problem as azrin1972.

fhb · 2021-06-06T17:03:59Z

This happens to me acactly too, tried a lot of things. Drivers are up to date. It's a ESP32-WROM with 30 Pins and USB/UART CH9102x.

``/Users/Felix/Library/Arduino15/packages/esp32/tools/esptool_py/3.0.0/esptool --chip esp32 --port /dev/cu.usbmodem52870049811 --baud 115200 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 40m --flash_size detect 0xe000 /Users/Felix/Library/Arduino15/packages/esp32/hardware/esp32/1.0.6/tools/partitions/boot_app0.bin 0x1000 /Users/Felix/Library/Arduino15/packages/esp32/hardware/esp32/1.0.6/tools/sdk/bin/bootloader_qio_40m.bin 0x10000 /var/folders/br/k52zl5l16bgg65qt6cqzmm9r0000gn/T/arduino_build_58002/sketch_jun06c.ino.bin 0x8000 /var/folders/br/k52zl5l16bgg65qt6cqzmm9r0000gn/T/arduino_build_58002/sketch_jun06c.ino.partitions.bin
esptool.py v3.0-dev
Serial port /dev/cu.usbmodem52870049811
Connecting....
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 3c:61:05:14:e8:14
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 01070000)
A fatal error occurred: Failed to write to target RAM (result was 01070000)
``

lmayencourt · 2021-06-10T19:12:31Z

I'm facing the same issue with a few ESP32 DEVKITV1 I got from aliexpress:

esptool.py v2.6
Serial port /dev/cu.usbmodem52870048231
Connecting......
Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
MAC: 3c:61:05:14:57:34
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 01070000)
A fatal error occurred: Failed to write to target RAM (result was 01070000)

Any hint to resolve this?

azrin1972 · 2021-06-11T00:41:58Z

I've contacted LilyGo and it seems the FTDI chip they are using is not compatible with Mac OS Big Sur UART Driver. My solution right now is yo use windows under Virtual box and flat from Windows.

Hope this helps

glowingkitty · 2021-06-13T12:22:35Z

@azrin1972 cannot even get it to work under a virtual machine with windows 10... Any update on how to make it work on MacOS Big Sur? (M1 Mac)
Else I guess I need to return the ESP32 from LilyGo... Or do you know what the best way is to message them?

don41382 · 2021-06-13T16:09:39Z

At first I thought the chip is broken. But yes, I am running on a M1 too and get the same error. Did anyone contact LilyGo already?

fhb · 2021-06-13T16:22:06Z

For me this error occurs on an older Intel machine running MacOS Big Sur. I didn't try flashing with virtual machine and windows 10 yet, will do in a few days though and report.

don41382 · 2021-06-13T19:37:52Z

@fhb I used Parallels Software on my M1 running Windows 10.

I could upload the image without any issues.

solocatz · 2021-06-15T00:41:28Z

I've contacted LilyGo and it seems the FTDI chip they are using is not compatible with Mac OS Big Sur UART Driver. My solution right now is yo use windows under Virtual box and flat from Windows.

Hope this helps

I might got same issue here, Intel CPU with MacOS 11.4 .
For me only affect Lilygo product, my other low cost esp32 clones are fine.

esptool.py v3.0-dev
Serial port /dev/cu.usbmodem526F0051341
Connecting........__
Chip is ESP32-D0WDQ6-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 08:3a:f2:47:3b:2c
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 01070000)
A fatal error occurred: Failed to write to target RAM (result was 01070000)

squix78 · 2021-08-28T12:49:41Z

I had the same issue with a LilyGO device with CH9102 UART chip. The driver in this github resolved the issue for me completely on Mac OS X 11.5.2 Big Sur: Xinyuan-LilyGO/LilyGo-T-Call-SIM800#139 But be warned: you have to install a driver and trust it in the security settings. All driver installation instructions are in Chinese 😱

wangkangman · 2021-09-15T11:31:42Z

I think it must be something wrong with the big Sur that every thing running well at windows on same pc with another disk.

Sladerix · 2021-10-22T17:56:16Z

I had the same issue with a LilyGO device with CH9102 UART chip. The driver in this github resolved the issue for me completely on Mac OS X 11.5.2 Big Sur: Xinyuan-LilyGO/LilyGo-T-Call-SIM800#139 But be warned: you have to install a driver and trust it in the security settings. All driver installation instructions are in Chinese 😱

Thanks! it worked on Big Sur 11.6 too

BaltarJoaoPaulo · 2022-06-27T13:04:11Z

I solved this problem changing the ESP01 USB adapter

esptool.FatalError: Failed to write to target RAM (result was 0107)

the problem was in the USB-SERIAL converter

bytemain · 2022-06-29T11:27:31Z

I had the same issue with a LilyGO device with CH9102 UART chip. The driver in this github resolved the issue for me completely on Mac OS X 11.5.2 Big Sur: Xinyuan-LilyGO/LilyGo-T-Call-SIM800#139 But be warned: you have to install a driver and trust it in the security settings. All driver installation instructions are in Chinese 😱

download this new driver is worked for me !!!

http://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html

and you need select the new port

raulclaudino · 2022-07-26T04:13:42Z

I had the same issue with a LilyGO device with CH9102 UART chip. The driver in this github resolved the issue for me completely on Mac OS X 11.5.2 Big Sur: Xinyuan-LilyGO/LilyGo-T-Call-SIM800#139 But be warned: you have to install a driver and trust it in the security settings. All driver installation instructions are in Chinese 😱

download this new driver is worked for me !!!

http://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html

and you need select the new port

English version:
http://www.wch-ic.com/downloads/CH34XSER_MAC_ZIP.html

kanstantsin-bucha · 2023-05-31T06:54:40Z

This issue keeps coming - I have it on the ESP32C3 board for the serial monitor USB-C, I am glad I have the second straight from chip USC-C that does the job. For me, it means I should plug both USB-C when writing firmware. Why do they use that CH9102 UART chip in the first place? I used to buy boards with CP210x and never had a single problem.

gkuhlmann14 · 2023-07-13T12:51:58Z

I had the same issue with a LilyGO device with CH9102 UART chip. The driver in this github resolved the issue for me completely on Mac OS X 11.5.2 Big Sur: Xinyuan-LilyGO/LilyGo-T-Call-SIM800#139 But be warned: you have to install a driver and trust it in the security settings. All driver installation instructions are in Chinese 😱

download this new driver is worked for me !!!
http://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html
and you need select the new port

English version: http://www.wch-ic.com/downloads/CH34XSER_MAC_ZIP.html

If you're using platformio I would recommend the following setting in your platformio.ini file: upload_port = /dev/cu.wchusbserialxxxxxxxxx (where xxxxxxxxx is the serial # from the downloaded chinese driver which you can find in either /dev folder or your computers System Information as detailed below). I was experiencing issues with auto detecting upload port for my board and after hard coding to the driver in the ini file no fatal error.

Rob2 · 2023-08-05T15:50:04Z

'A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out)'

This problem was solved for me on an old Macbook Air running macOS 10.13.6 connected to an 'M5Stack Tough' with ESP32-D0WDQ6-V3 by updating to the latest driver for the CH9102 USB/UART chip that the 'Tough' uses.

Fully documented driver downloads for various commonly used WCH chips are available here https://wch-ic.com/products/categories/46.html?pid=1#data

mrsndmn · 2024-01-31T18:52:56Z

I had a similar problem on Mac with ESP32-C6-DevKitC-1-N4 ESP32-C6 RISC-V ESP32

This board has two usb-c ports. And problem was solved by connecting to the second port ESP32C6)

christiangda · 2024-03-17T13:58:53Z

Same issue for this ESP32-S3 N16R8

and after read and install this on my MacBook Pro M1 https://www.wch.cn/downloads/CH34XSER_MAC_ZIP.html start working.

Thanks to @raulclaudino for shared the link and info

pauljmartinez · 2024-07-01T00:55:21Z

I also had this issue. I'm on an Apple M1 Max, Sonoma 14.5 (23F79) and was getting this error when uploading to my ESP32-C6-DEV-KIT-N8.

esptool.py v4.6
Serial port /dev/cu.usbmodem57350148971
Connecting....
Chip is ESP32-C6 (QFN40) (revision v0.0)
Features: WiFi 6, BT 5, IEEE802.15.4
Crystal is 40MHz
MAC: 40:4c:ca:4f:90:b0:ff:fe
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out)
Failed uploading: uploading error: exit status 2

However, I hadn't noticed that there were 2 new dev/cu.* entries added when connecting my ESP via the one USB-C port.

$  ls -l /dev/cu*
crw-rw-rw- 1 root wheel 9, 5 Jun 17 09:56 /dev/cu.Bluetooth-Incoming-Port
crw-rw-rw- 1 root wheel 9, 3 Jun 30 16:24 /dev/cu.usbmodem57350148971
crw-rw-rw- 1 root wheel 9, 1 Jun 30 17:42 /dev/cu.wchusbserial57350148971

Choosing the second entry in Arduino IDE solved my issue.
/dev/cu.wchusbserial57350148971

sridhar2rok · 2024-09-24T14:19:58Z

I had a similar problem on Mac with ESP32-C6-DevKitC-1-N4 ESP32-C6 RISC-V ESP32

This board has two usb-c ports. And problem was solved by connecting to the second port ESP32C6)

followed the same using second usb-c port solved the issue

projectgus closed this as completed Mar 13, 2018

github-actions bot changed the title ~~A fatal error occurred: Failed to write to target RAM (result was 0107)~~ A fatal error occurred: Failed to write to target RAM (result was 0107) (ESPTOOL-95) Dec 8, 2020

dobairoland mentioned this issue Mar 29, 2021

cannot upload stub - write to RAM error 0107 (ESPTOOL-221) #617

Closed

solocatz mentioned this issue Jun 15, 2021

MacBook Intel CPU with MacOS 11.4 (Big Sur) can not upload anything to T5 board Xinyuan-LilyGO/LilyGo-T5-Epaper-Series#16

Closed

timbodeit mentioned this issue Oct 24, 2021

Problem with ESP32 (ESPRESSIF) seemoo-lab/openhaystack#66

Closed

radimkarnis mentioned this issue Aug 22, 2023

A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out) (ESPTOOL-725) #908

Closed

1 task

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

A fatal error occurred: Failed to write to target RAM (result was 0107) (ESPTOOL-95) #280

A fatal error occurred: Failed to write to target RAM (result was 0107) (ESPTOOL-95) #280

emeyedeejay commented Mar 2, 2018

projectgus commented Mar 13, 2018

emeyedeejay commented Mar 13, 2018

projectgus commented Mar 13, 2018

vgonet commented Aug 29, 2018

stigok commented Oct 21, 2018 •

edited

Loading

sandikodev commented Jan 30, 2020

tneish commented Apr 12, 2020

alunomakerdigital commented Dec 8, 2020

azrin1972 commented May 23, 2021

lordofswe commented May 27, 2021 •

edited

Loading

fhb commented Jun 6, 2021 •

edited

Loading

lmayencourt commented Jun 10, 2021

azrin1972 commented Jun 11, 2021

glowingkitty commented Jun 13, 2021

don41382 commented Jun 13, 2021

fhb commented Jun 13, 2021

don41382 commented Jun 13, 2021

solocatz commented Jun 15, 2021

squix78 commented Aug 28, 2021

wangkangman commented Sep 15, 2021

Sladerix commented Oct 22, 2021

BaltarJoaoPaulo commented Jun 27, 2022

bytemain commented Jun 29, 2022

raulclaudino commented Jul 26, 2022

kanstantsin-bucha commented May 31, 2023

gkuhlmann14 commented Jul 13, 2023

Rob2 commented Aug 5, 2023

mrsndmn commented Jan 31, 2024

christiangda commented Mar 17, 2024

pauljmartinez commented Jul 1, 2024

sridhar2rok commented Sep 24, 2024

A fatal error occurred: Failed to write to target RAM (result was 0107) (ESPTOOL-95) #280

A fatal error occurred: Failed to write to target RAM (result was 0107) (ESPTOOL-95) #280

Comments

emeyedeejay commented Mar 2, 2018

Full esptool.py command line as run: python esptool.py --port COM3 read_flash 0x00000 0x100000 image1M.bin

Full output from esptool.py (please copy and paste all lines of output) D:\Downloads\esptool-2.3.1>python esptool.py --port COM3 read_flash 0x00000 0x100000 image1M.bin

What is the expected behaviour? Backup of current firmware

Do you have any other information from investigating this? Tried with 2 different USB -> Serial devices. FTDI232 and PROLIFIC USB-to-serail adapter

Is there any other information you can think of which will help us reproduce this problem?

projectgus commented Mar 13, 2018

emeyedeejay commented Mar 13, 2018

projectgus commented Mar 13, 2018

vgonet commented Aug 29, 2018

stigok commented Oct 21, 2018 • edited Loading

sandikodev commented Jan 30, 2020

tneish commented Apr 12, 2020

alunomakerdigital commented Dec 8, 2020

azrin1972 commented May 23, 2021

lordofswe commented May 27, 2021 • edited Loading

fhb commented Jun 6, 2021 • edited Loading

lmayencourt commented Jun 10, 2021

azrin1972 commented Jun 11, 2021

glowingkitty commented Jun 13, 2021

don41382 commented Jun 13, 2021

fhb commented Jun 13, 2021

don41382 commented Jun 13, 2021

solocatz commented Jun 15, 2021

squix78 commented Aug 28, 2021

wangkangman commented Sep 15, 2021

Sladerix commented Oct 22, 2021

BaltarJoaoPaulo commented Jun 27, 2022

bytemain commented Jun 29, 2022

raulclaudino commented Jul 26, 2022

kanstantsin-bucha commented May 31, 2023

gkuhlmann14 commented Jul 13, 2023

Rob2 commented Aug 5, 2023

mrsndmn commented Jan 31, 2024

christiangda commented Mar 17, 2024

pauljmartinez commented Jul 1, 2024

sridhar2rok commented Sep 24, 2024

stigok commented Oct 21, 2018 •

edited

Loading

lordofswe commented May 27, 2021 •

edited

Loading

fhb commented Jun 6, 2021 •

edited

Loading