<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[[OSX Big Sur] Core2 Failed to write to target RAM (result was 01070000)]]></title><description><![CDATA[<p dir="auto">Hi, I'm attempting to program an M5Stack Core2 on a Mac running Big Sur.  Whether I use <a href="http://esptool.py" target="_blank" rel="noopener noreferrer nofollow ugc">esptool.py</a> with Arduino or with esp-idf, I get the same error:</p>
<p dir="auto"><code>A fatal error occurred: Failed to write to target RAM (result was 01070000)</code></p>
<p dir="auto">I've tried several baud rates.</p>
<p dir="auto">When I use my Linux laptop, there are no issues with programming the same device with the same cable.</p>
<p dir="auto">I'm using the latest version of the CP210x VCP drivers (I've tried the version available from M5 and directly from Silabs (they seem the same; version 6.0.1).  The device does show up as a serial device: /dev/tty.usbmodem52D20295411.  But this is suspicious... it shows up that way whether I have the CP210x drivers loaded or not.  On a Mac I'm not sure how to determine which driver a serial device is using.</p>
<p dir="auto">Here's some relevant links, just in case someone else is having the same problem.</p>
<ul>
<li>Re: <a href="/topic/2175/new-m5stack-failed-to-write-to-target-ram-result-was-01070000">new m5stack: Failed to write to target RAM (result was 01070000)</a></li>
<li><a href="https://silabs-prod.adobecqms.net/community/interface/forum.topic.html/cp210x_vcp_driverformacosbigsurv111notinst-gYuR" target="_blank" rel="noopener noreferrer nofollow ugc">https://silabs-prod.adobecqms.net/community/interface/forum.topic.html/cp210x_vcp_driverformacosbigsurv111notinst-gYuR</a></li>
</ul>
]]></description><link>https://community.m5stack.com/topic/3568/osx-big-sur-core2-failed-to-write-to-target-ram-result-was-01070000</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 09:37:01 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/3568.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 07 Sep 2021 17:58:23 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to [OSX Big Sur] Core2 Failed to write to target RAM (result was 01070000) on Wed, 08 Dec 2021 07:15:31 GMT]]></title><description><![CDATA[<p dir="auto">This is an ongoing issue with OSX and it seams the only cure at present is to upgrade to OSX 10.16, something I'm not ready to do yet.</p>
]]></description><link>https://community.m5stack.com/post/15757</link><guid isPermaLink="true">https://community.m5stack.com/post/15757</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Wed, 08 Dec 2021 07:15:31 GMT</pubDate></item><item><title><![CDATA[Reply to [OSX Big Sur] Core2 Failed to write to target RAM (result was 01070000) on Tue, 07 Dec 2021 21:35:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/egradman" aria-label="Profile: egradman">@<bdi>egradman</bdi></a> said in <a href="/post/14832">[OSX Big Sur] Core2 Failed to write to target RAM (result was 01070000)</a>:</p>
<blockquote>
<p dir="auto">new m5stack: Failed to write to target RAM (result was 01070000)<br />
I am having the same problem, did you manage to fix it?</p>
</blockquote>
]]></description><link>https://community.m5stack.com/post/15752</link><guid isPermaLink="true">https://community.m5stack.com/post/15752</guid><dc:creator><![CDATA[slugs]]></dc:creator><pubDate>Tue, 07 Dec 2021 21:35:44 GMT</pubDate></item></channel></rss>