<?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[M5stack Grey dead]]></title><description><![CDATA[<p dir="auto">Hi, I have both Grey and Core2 modules. When playing with them I made a mistake and burned an image compiled for Core2 to my Grey device. And Grey is dead :(<br />
I have tried to erase and burn e.g. UIFlow using M5burner but the serial connection (via USB) shows timeout. Is there any chance to bring my Grey back alive? Any suggestions?</p>
]]></description><link>https://community.m5stack.com/topic/5989/m5stack-grey-dead</link><generator>RSS for Node</generator><lastBuildDate>Fri, 15 May 2026 05:45:51 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/5989.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 16 Jan 2024 15:54:41 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to M5stack Grey dead on Wed, 17 Jan 2024 06:07:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/rafciuk" aria-label="Profile: rafciuk">@<bdi>rafciuk</bdi></a> When the connecting screen appears, Hold the reset button in for around 5 seconds. it takes some practice but the grey is not dead just soft bricked.<br />
Another option is to try using arduino to upload a blank sketch before trying M5Burner again.</p>
<p dir="auto">I have accidentally uploaded the wrong firmware before and had to reset in the above manner.</p>
<p dir="auto">The device is not dead it just that the core and core2 use different screens and so you cant see what it is doing.</p>
]]></description><link>https://community.m5stack.com/post/23372</link><guid isPermaLink="true">https://community.m5stack.com/post/23372</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Wed, 17 Jan 2024 06:07:45 GMT</pubDate></item></channel></rss>