<?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 Fire pinout]]></title><description><![CDATA[<p dir="auto">Background: I'm using <strong>M5Stack</strong> (the "normal" version) in conjunction with Mongoose-OS sucessfully, but now I've got a <strong>M5Stack Fire</strong> and without changes, the software won't run as there are now some GPIO pins used for other purposes, so I have to switch to other solutions. PSRAM works fine (to prevent mentioning this matter). But I didn't find any possibility to compare which GPIOs are used on the <strong>M5Stack</strong> and which on the <strong>M5Stack Fire</strong> (and their purposes) I only found the standard <strong>M5Stack</strong> pinouts - is there any chance of retreiving such a list?</p>
]]></description><link>https://community.m5stack.com/topic/301/m5stack-fire-pinout</link><generator>RSS for Node</generator><lastBuildDate>Sat, 14 Mar 2026 02:06:42 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/301.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 26 Aug 2018 15:22:07 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to M5Stack Fire pinout on Sat, 08 Sep 2018 07:37:30 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/328">@mamuesp</a><br />
The Fire comes with a small leaflet in the box. Check the Schematic page for GPIO numbers of connected devices.</p>
]]></description><link>https://community.m5stack.com/post/1494</link><guid isPermaLink="true">https://community.m5stack.com/post/1494</guid><dc:creator><![CDATA[HansvL]]></dc:creator><pubDate>Sat, 08 Sep 2018 07:37:30 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stack Fire pinout on Sat, 08 Sep 2018 06:15:24 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/328">@mamuesp</a> 在 <a href="/post/1491">M5Stack Fire pinout</a> 中说：</p>
<blockquote>
<p dir="auto">Unfortunately there is no help in this matter?</p>
</blockquote>
<p dir="auto">What is the conflict?<br />
Is a device address issue?<br />
Have you tried changing the address of the items on i2c?</p>
]]></description><link>https://community.m5stack.com/post/1493</link><guid isPermaLink="true">https://community.m5stack.com/post/1493</guid><dc:creator><![CDATA[ajb2k3]]></dc:creator><pubDate>Sat, 08 Sep 2018 06:15:24 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stack Fire pinout on Fri, 07 Sep 2018 18:08:15 GMT]]></title><description><![CDATA[<p dir="auto">Unfortunately there is no help in this matter?</p>
]]></description><link>https://community.m5stack.com/post/1491</link><guid isPermaLink="true">https://community.m5stack.com/post/1491</guid><dc:creator><![CDATA[mamuesp]]></dc:creator><pubDate>Fri, 07 Sep 2018 18:08:15 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stack Fire pinout on Sun, 26 Aug 2018 16:49:05 GMT]]></title><description><![CDATA[<p dir="auto">Thanks, but I'm already aware of this fact (it's the same on the <strong>ODROID-GO</strong>), but there has to be some other conflicts when using standard <strong>I2C</strong>. Because my setings runs on <strong>M5Stack</strong> and (with some adaptions) on <strong>ODROID-GO</strong>, but not on <strong>M5Stack Fire</strong></p>
]]></description><link>https://community.m5stack.com/post/1448</link><guid isPermaLink="true">https://community.m5stack.com/post/1448</guid><dc:creator><![CDATA[mamuesp]]></dc:creator><pubDate>Sun, 26 Aug 2018 16:49:05 GMT</pubDate></item><item><title><![CDATA[Reply to M5Stack Fire pinout on Sun, 26 Aug 2018 16:34:42 GMT]]></title><description><![CDATA[<p dir="auto"><a class="mention plugin-mentions-user plugin-mentions-a" href="https://community.m5stack.com/uid/328">@mamuesp</a></p>
<p dir="auto">You cannot use GPIOs 16&amp;17 on M5Stack with psRAM as they are used to access psRAM.</p>
]]></description><link>https://community.m5stack.com/post/1447</link><guid isPermaLink="true">https://community.m5stack.com/post/1447</guid><dc:creator><![CDATA[loboris]]></dc:creator><pubDate>Sun, 26 Aug 2018 16:34:42 GMT</pubDate></item></channel></rss>