<?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[Topics tagged with cores3]]></title><description><![CDATA[A list of topics that have been tagged with cores3]]></description><link>https://community.m5stack.com/tags/cores3</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 15:01:42 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/tags/cores3.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 09 Mar 2026 17:40:26 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Issue with unit 4 relay on cores3]]></title><description><![CDATA[On the cores3 (module connected through port A), I see no devices found on i2c scan when using esphome. It finds OK on the atom-lite.
If using the "Cores3 test" binary from m5stack, I can see the address found on the i2c scan app.
]]></description><link>https://community.m5stack.com/topic/8126/issue-with-unit-4-relay-on-cores3</link><guid isPermaLink="true">https://community.m5stack.com/topic/8126/issue-with-unit-4-relay-on-cores3</guid><dc:creator><![CDATA[ngolf]]></dc:creator><pubDate>Mon, 09 Mar 2026 17:40:26 GMT</pubDate></item><item><title><![CDATA[CoreS3 read data via usb_uart]]></title><link>https://community.m5stack.com/topic/8078/cores3-read-data-via-usb_uart</link><guid isPermaLink="true">https://community.m5stack.com/topic/8078/cores3-read-data-via-usb_uart</guid><pubDate>Tue, 10 Feb 2026 21:14:46 GMT</pubDate></item><item><title><![CDATA[Demo Sketches for Module USB V1.2 do not compile or link]]></title><link>https://community.m5stack.com/topic/7808/demo-sketches-for-module-usb-v1-2-do-not-compile-or-link</link><guid isPermaLink="true">https://community.m5stack.com/topic/7808/demo-sketches-for-module-usb-v1-2-do-not-compile-or-link</guid><pubDate>Tue, 09 Sep 2025 13:55:26 GMT</pubDate></item><item><title><![CDATA[CoreS3 and unit CatM GNSS cannot cooperate]]></title><description><![CDATA[Felix @felmue OMG, this was so easy...many thanks, that was the reason why the unit wasn't reacting for any commands. Have a nice day
]]></description><link>https://community.m5stack.com/topic/6282/cores3-and-unit-catm-gnss-cannot-cooperate</link><guid isPermaLink="true">https://community.m5stack.com/topic/6282/cores3-and-unit-catm-gnss-cannot-cooperate</guid><dc:creator><![CDATA[jaro99]]></dc:creator><pubDate>Sun, 31 Mar 2024 21:35:46 GMT</pubDate></item><item><title><![CDATA[M5 CoreS3 power drain issue.]]></title><description><![CDATA[I recall the last action before I started to have the issue and I now suspect it was my particular scenario of charging the din base battery that might have damaged one or more of the power distribution mosfets. I shall describe the scenario here as a caution for fellow core s3 owners.
firmware installed: uiflow 2.0.1
external device connected: M5Stack GPS/BDS unit connected to port c at the din base.
charger used: wall charger with multiple usb c and a ports. one of the usb c port was used.
sequence of event:

a gps related uiflow program was running and the battery dropped low
connected the wall charger to the core s3 with a usb c to c cable to charge the battery inside the din base
after some time switched off the core s3 by holding the power button while the charging is still going on
core s3 felt very warm to the touch but I did not think too much of it.
charging was completed after the red indicator turned off

I suspected that in sequence 4 one or more mosfets were overheated and damaged.
]]></description><link>https://community.m5stack.com/topic/6196/m5-cores3-power-drain-issue</link><guid isPermaLink="true">https://community.m5stack.com/topic/6196/m5-cores3-power-drain-issue</guid><dc:creator><![CDATA[lweiyen]]></dc:creator><pubDate>Tue, 12 Mar 2024 02:20:26 GMT</pubDate></item></channel></rss>