<?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 base]]></title><description><![CDATA[A list of topics that have been tagged with base]]></description><link>https://community.m5stack.com/tags/base</link><generator>RSS for Node</generator><lastBuildDate>Tue, 28 Apr 2026 23:05:07 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/tags/base.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 06 Nov 2019 20:48:45 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[WiFi Connection Failure when using &quot;GO&quot; Base &#x2F; Bottom]]></title><description><![CDATA[Thanks @alextil
I'm glad I haven't (completely) lost my mind.
I haven't had any progress with this issue besides creating a workaround with a Proto and some Grove ports- assembling a sort of..."Port Board." It certainly isn't pretty, but here's a pic for fun:
[image: 1575484626076-portboard-cc.jpg]
It's 2 "Port B"s - to accommodate devices that want GP26, GP36, or BOTH. And a simple male header to Serial2. (16/17)
I've had some thoughts on other things to try (mostly in configuration or digging deeper into M5 and ESP32 libraries), but have been busy with another project that requires much smaller hardware. If you (or anyone) find something that in any way changes this functionality, please post.
All info helps.
-Atlas
]]></description><link>https://community.m5stack.com/topic/1452/wifi-connection-failure-when-using-go-base-bottom</link><guid isPermaLink="true">https://community.m5stack.com/topic/1452/wifi-connection-failure-when-using-go-base-bottom</guid><dc:creator><![CDATA[Kindly_Atlas]]></dc:creator><pubDate>Wed, 06 Nov 2019 20:48:45 GMT</pubDate></item></channel></rss>