new m5stack: Failed to write to target RAM (result was 01070000)

Mackone

@erich I'm on Mojave 10.14 and problem still exists :/

ajb2k3

I’m actually getting it with Catalina

slugs

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

Exie

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.html

Confirmed, installing the driver from this thread here worked for me
https://github.com/Xinyuan-LilyGO/LilyGo-T-Call-SIM800/issues/139

erich

@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.html

Confirmed, installing the driver from this thread here worked for me
https://github.com/Xinyuan-LilyGO/LilyGo-T-Call-SIM800/issues/139

I guess you're right as I noticed on banggood/ aliexpress some products using this CH9102 chip are tagged as not Mac compatible.

labixiaoxin8888

@mackone try connecting the downloader's 3V3 to Stamp Pico's 5V

parahooner

I found a solution that works on Montery :-)

Make sure you follow the PDF instructions, this works M1 Mac M5 Epaper

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

Bludotz

@parahooner Very many thanks for posting this, it completely resolved the problem.

drjakob

I still have the same problem with 5 new M5Fire on Big Sur. Two older ones burned succesful.

ajb2k3

@drjakob Check which USB driver is in the new cores as the driver chip was changed due to the part shortage.