new m5stack: Failed to write to target RAM (result was 01070000)
-
Hello,
I'm also new with M5Stack products and have got the very same issue with a brand new Core 2.
I am using VSCode + PlatformIO
I am currently trying to test some basic code but end up with the same error when uploading my code.
Have you solve the issue? Do you know what was the cause?
Thanks
Eric -
Hi @erich , could you please send me an email so I could assist you regarding this issue: roni@m5stack.com so I could assist you better?
-
@zontex Thanks a lot! Email sent with the full explanation of the issue
-
Hello @Zontex could you advise me also as I got a similar problem
Start Burn
--chip esp32 --port /dev/tty.usbmodem51850037101 --baud 1500000 --before default_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x7ff000 /Applications/M5Burner.app/Contents/Resources/packages/fw/other/wifi.bin 0x1000 /Applications/M5Burner.app/Contents/Resources/packages/fw/core/UIFlow_Core2-v1.8.5-core2.bin
esptool.py v2.5.0
Serial port /dev/tty.usbmodem51850037101
Connecting...
.Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
MAC: 08......HIDINGIT
Uploading stub...A fatal error occurred: Failed to write to target RAM (result was 01070000)
Burn Failed
I guess it is the driver not loading well as I can only see this tty of type modem but I have found no easy way to make it working, I am using the Apple Multi Adaptor (HDMI/USB) on USB C.
-
I have installed latest driver https://www.silabs.com/documents/public/software/Mac_OSX_VCP_Driver.zip and can see the corresponding extension in /Library/Extensions with
drwxr-xr-x@ 3 root wheel 96 Oct 15 10:46 SiLabsUSBDriver.kext
but then when running M5Burner it only show a tty device of type Bluetooth or usb modem
ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port
/dev/tty.usbmodem51850037101I am running macOS Catalina
-
@darul75 said in new m5stack: Failed to write to target RAM (result was 01070000):
I have installed latest driver https://www.silabs.com/documents/public/software/Mac_OSX_VCP_Driver.zip and can see the corresponding extension in /Library/Extensions with
drwxr-xr-x@ 3 root wheel 96 Oct 15 10:46 SiLabsUSBDriver.kext
but then when running M5Burner it only show a tty device of type Bluetooth or usb modem
ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port
/dev/tty.usbmodem51850037101I am running macOS Catalina
/dev/tty.usbmodem51850037101 is the correct device, I'm not sure what's going on in OSX but this is how it appears for me and the device that works for me.
-
Great thanks, I will try again later, in the meantime I switched to a Windows machine to make it working.
-
I had weird problems like this with an M5Stamp-PICO until I put more capacitance across the bus (5V and 3.3V). I used a couple of tantalum capacitors I had on hand, not sure the value, probably 33uF. I was powering the device through the USB serial adapter and apparently it was power limited.
I have had no problem whatsoever since then. -
@ajb2k3
Same thing is happening to me:Start Burn
"
--chip esp32 --port /dev/tty.usbmodem53190095701 --baud 1500000 --before default_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 /Applications/M5Burner.app/Contents/Resources/packages/fw/core/Core2_Tools-v1.0.0.binesptool.py v2.5.0
Serial port /dev/tty.usbmodem53190095701
Connecting...Chip is ESP32D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse
MAC: 08:3a:f2:66:b7:70
Uploading stub...A fatal error occurred: Failed to write to target RAM (result was 01070000)
Burn Failed
"Fighting for over 10 hours.. I'm dying here..
-
Same here - Have You found any solution?
-
This was a known issue with Big Sur (something related to the python and / or serial port implementation in Big Sur.
I did contact M5Stack support but no solution has ever been found.
I gave up and reverted back to Catalina and it worked fine again.
Now I just installed the latest Monterey but haven't tested the Core2 yet.
In the meantime I was also using a windows computer.... -
@erich I'm on Mojave 10.14 and problem still exists :/
-
I’m actually getting it with Catalina
-
Has anyone managed to get the core 2 to work with an M1 mac? I think that you do not need the driver for the m1? With a m5stick C it works fine, but not with the core 2
-
I have the same issue when I use the M5Stack ESP32 Downloader.
However when I use a simple M5Stack Atom Matrix, its works fine.I am on OSX Big Sir.
I feel like the issue is related to the CH9102 chip on the ESP32 Downloader where the Atom has the CP2104 I think.
This theory is supported by this article here:
https://blog.squix.org/2021/08/ch9102-driver-issues-failed-to-write-to-target-ram.htmlConfirmed, installing the driver from this thread here worked for me
https://github.com/Xinyuan-LilyGO/LilyGo-T-Call-SIM800/issues/139 -
@exie said in new m5stack: Failed to write to target RAM (result was 01070000):
I have the same issue when I use the M5Stack ESP32 Downloader.
However when I use a simple M5Stack Atom Matrix, its works fine.I am on OSX Big Sir.
I feel like the issue is related to the CH9102 chip on the ESP32 Downloader where the Atom has the CP2104 I think.
This theory is supported by this article here:
https://blog.squix.org/2021/08/ch9102-driver-issues-failed-to-write-to-target-ram.htmlConfirmed, installing the driver from this thread here worked for me
https://github.com/Xinyuan-LilyGO/LilyGo-T-Call-SIM800/issues/139I guess you're right as I noticed on banggood/ aliexpress some products using this CH9102 chip are tagged as not Mac compatible.
-
@mackone try connecting the downloader's 3V3 to Stamp Pico's 5V
-
I found a solution that works on Montery :-)
Make sure you follow the PDF instructions, this works M1 Mac M5 Epaper
-
@parahooner Very many thanks for posting this, it completely resolved the problem.
-
I still have the same problem with 5 new M5Fire on Big Sur. Two older ones burned succesful.
