<?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[Correct I2C problems with PaHUB]]></title><description><![CDATA[<p dir="auto">PaHUB does not work with CORE2, always the same message "name 'freq' isn't defined.<br />
All these situations block any progress with M5stack products and add more and more frustration day after day.<br />
Please, more testing before release to market.</p>
]]></description><link>https://community.m5stack.com/topic/2958/correct-i2c-problems-with-pahub</link><generator>RSS for Node</generator><lastBuildDate>Wed, 29 Apr 2026 01:00:14 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/2958.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 15 Feb 2021 18:02:06 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Correct I2C problems with PaHUB on Fri, 12 Mar 2021 17:00:08 GMT]]></title><description><![CDATA[<p dir="auto">the I2C bug with the PaHub has not been corrected in version 1.7.3 !!!!.<br />
Isn't it serious to market products that don't work?</p>
]]></description><link>https://community.m5stack.com/post/12956</link><guid isPermaLink="true">https://community.m5stack.com/post/12956</guid><dc:creator><![CDATA[Arno]]></dc:creator><pubDate>Fri, 12 Mar 2021 17:00:08 GMT</pubDate></item><item><title><![CDATA[Reply to Correct I2C problems with PaHUB on Fri, 19 Feb 2021 15:58:57 GMT]]></title><description><![CDATA[<p dir="auto">Hello again, M5Stack engineers</p>
<p dir="auto">I did some additional tests and the issue has been introduced in M5Core2 firmware 1.7.2. When I use UIFlow 1.7.2 (online) with M5Core2 firmware 1.7.0 or 1.7.1.1 it works as expected (1.7.1 was broken in other aspects)</p>
<p dir="auto">In other words, only the latest M5Core2 firmware 1.7.2 is affected by this bug.</p>
<p dir="auto">May I humbly suggest you spend some time and improve your regression tests? It's bad enough if something doesn't work for a new device, but it is outright annoying if something that has worked in an earlier firmware version gets broken in a subsequent version.</p>
<p dir="auto">Thank you for listening.</p>
<p dir="auto">Regards<br />
Felix</p>
]]></description><link>https://community.m5stack.com/post/12568</link><guid isPermaLink="true">https://community.m5stack.com/post/12568</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Fri, 19 Feb 2021 15:58:57 GMT</pubDate></item><item><title><![CDATA[Reply to Correct I2C problems with PaHUB on Thu, 18 Feb 2021 14:01:43 GMT]]></title><description><![CDATA[<p dir="auto">Hey M5stack engineers</p>
<p dir="auto">Since I was curious I got myself a PaHUB and I can confirm that using it with M5Core2 (firmware 1.7.2) in UiFlow 1.7.2 doesn't work at all and always returns the <code>name 'freq'</code> isn't defined error. (It works fine with M5Stack Gray btw.)</p>
<p dir="auto">Please either fix this issue or open source UiFlow so we can try to fix it ourselves.</p>
<p dir="auto">Thank you for listening.</p>
<p dir="auto">Felix</p>
]]></description><link>https://community.m5stack.com/post/12548</link><guid isPermaLink="true">https://community.m5stack.com/post/12548</guid><dc:creator><![CDATA[felmue]]></dc:creator><pubDate>Thu, 18 Feb 2021 14:01:43 GMT</pubDate></item></channel></rss>