<?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[Is my CoreS3 SE defective?]]></title><description><![CDATA[<p dir="auto">I just got the M5Stack CoreS3 SE and I'm having nothing but problems with it. I'm not sure if I'm doing something wrong, or if the unit I got is defective in some way.</p>
<p dir="auto">Out of the box, when I plugged it in, the demo app was working fine. I could see available Wi-Fi networks, draw on the screen in the Touch app, see the waveforms from the microphones, etc.</p>
<p dir="auto">I have Arduino 2.3.4 on a MacBook Air M2 running macOS Sequoia 15.3. I installed the M5Stack board manager 2.1.3 and the M5CoreS3 library 1.0.0 (and all its dependencies). I tried to upload the sketch under Examples &gt; M5CoreS3 &gt; Basic &gt; display.</p>
<p dir="auto">When I plug the unit in or press the reset button, the sketch appears to run for a split second, and then the screen goes blank (or occasionally, it displays different coloured vertical bars). This happens whether I plug it in to my computer or to a USB wall adapter, with different cables. However, I discovered that if I change the CPU frequency from 240 MHz to 160 MHz under the Tools menu, this sketch runs normally.</p>
<p dir="auto">Other things I have tried to install don't work at all, with the screen simply remaining black. This includes using the m5burner application to try and re-install the CoreS3SE UserDemo.</p>
<p dir="auto">Anything else I can try, or should I be asking for a refund?</p>
]]></description><link>https://community.m5stack.com/topic/7277/is-my-cores3-se-defective</link><generator>RSS for Node</generator><lastBuildDate>Sat, 07 Mar 2026 06:31:23 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/7277.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 08 Feb 2025 18:49:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Is my CoreS3 SE defective? on Thu, 13 Feb 2025 16:58:45 GMT]]></title><description><![CDATA[<p dir="auto">Update: M5Stack has finally responded to my emails, so we'll see where that goes.</p>
]]></description><link>https://community.m5stack.com/post/28210</link><guid isPermaLink="true">https://community.m5stack.com/post/28210</guid><dc:creator><![CDATA[rgsteele]]></dc:creator><pubDate>Thu, 13 Feb 2025 16:58:45 GMT</pubDate></item><item><title><![CDATA[Reply to Is my CoreS3 SE defective? on Wed, 12 Feb 2025 00:36:10 GMT]]></title><description><![CDATA[<p dir="auto">Thanks <a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/443">@ajb2k3</a>, that's what I feared. I bought it directly from M5Stack and I've sent them two emails but haven't received a reply, so I guess I need to initiate a chargeback.</p>
]]></description><link>https://community.m5stack.com/post/28177</link><guid isPermaLink="true">https://community.m5stack.com/post/28177</guid><dc:creator><![CDATA[rgsteele]]></dc:creator><pubDate>Wed, 12 Feb 2025 00:36:10 GMT</pubDate></item><item><title><![CDATA[Reply to Is my CoreS3 SE defective? on Tue, 11 Feb 2025 08:18:00 GMT]]></title><description><![CDATA[<p dir="auto">Have you tried EasyLoader files like "CoreS3 Factory Firmware Easyloader" from documents webpage?</p>
<p dir="auto"><a href="https://docs.m5stack.com/en/core/CoreS3" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/en/core/CoreS3</a></p>
]]></description><link>https://community.m5stack.com/post/28174</link><guid isPermaLink="true">https://community.m5stack.com/post/28174</guid><dc:creator><![CDATA[robski]]></dc:creator><pubDate>Tue, 11 Feb 2025 08:18:00 GMT</pubDate></item><item><title><![CDATA[Reply to Is my CoreS3 SE defective? on Tue, 11 Feb 2025 06:35:29 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/224777">@rgsteele</a> No, that all I can think off, you need to contact the person you brought it from for a replacement.</p>
]]></description><link>https://community.m5stack.com/post/28169</link><guid isPermaLink="true">https://community.m5stack.com/post/28169</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Tue, 11 Feb 2025 06:35:29 GMT</pubDate></item><item><title><![CDATA[Reply to Is my CoreS3 SE defective? on Sun, 09 Feb 2025 17:43:34 GMT]]></title><description><![CDATA[<p dir="auto">Hi <a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/443">@ajb2k3</a>, thanks for responding.</p>
<p dir="auto">I just tried doing an erase and then burning the UIFlow2.0 image. As with the CoreS3 SE UserDemo, the burn completes successfully, but nothing is displayed on the screen whether I reset it with the button or unplug and plug it back in.</p>
<p dir="auto">If I connect with the serial monitor, however, the following is displayed:</p>
<pre><code>[FROM M5Burner] /dev/tty.usbmodem1401 opened.

       _  __ _               
 _   _(_)/ _| | _____      __
| | | | | |_| |/ _ \ \ /\ / /
| |_| | |  _| | (_) \ V  V / 
 \__,_|_|_| |_|\___/ \_/\_/  V2.2.1
</code></pre>
<p dir="auto">Is there something else I should be doing?</p>
]]></description><link>https://community.m5stack.com/post/28159</link><guid isPermaLink="true">https://community.m5stack.com/post/28159</guid><dc:creator><![CDATA[rgsteele]]></dc:creator><pubDate>Sun, 09 Feb 2025 17:43:34 GMT</pubDate></item><item><title><![CDATA[Reply to Is my CoreS3 SE defective? on Sun, 09 Feb 2025 08:11:23 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/224777">@rgsteele</a> Have you tried <strong>ERASE</strong> first in M5Burner and then burning UIFlow2?</p>
]]></description><link>https://community.m5stack.com/post/28156</link><guid isPermaLink="true">https://community.m5stack.com/post/28156</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Sun, 09 Feb 2025 08:11:23 GMT</pubDate></item></channel></rss>