<?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[Bottom2 and M144 ES8388 Audio Module I2S Bus Conflict]]></title><description><![CDATA[<p dir="auto"><strong>Please, add a switch on Bottom 2 to disconnect the SPM1423 I2S lines or to switch the ENABLE pin to solve the I2S Bus conflict.</strong></p>
<p dir="auto">The Bottom2 module includes a SPM1423 MEMS microphone, which uses:</p>
<pre><code>GPIO0 (BUS pin 24) for the clock signal (CLK)

GPIO34 (BUS pin 26) for the data signal (DAT, digital output)
</code></pre>
<p dir="auto">The Audio Module, based on the ES8388 codec, uses:</p>
<pre><code>GPIO0 (BUS pin 24) for I2S_MCLK

GPIO34 (BUS pin 26) for I2S_MAIN_DIN
</code></pre>
<p dir="auto">This creates a fundamental hardware conflict on the I2S bus.<br />
The Core Conflict</p>
<p dir="auto">Two independent devices attempt to drive the same data line:</p>
<pre><code>The ES8388 (M144 Audio Module) uses GPIO34 to send digitized audio data from its ADC (line-in or microphone) to the ESP32 via I2S.

The SPM1423 (Bottom2) uses the same GPIO34 to output PDM audio data from its internal MEMS microphone.
</code></pre>
<p dir="auto">More about this here: <a href="https://yo3hjv.substack.com/p/i2s-bus-conflict-between-m5stack" target="_blank" rel="noopener noreferrer nofollow ugc">I2S Bus Conflict Between M5Stack Core2 Audio Module and Bottom2</a></p>
<p dir="auto">Thank you,<br />
Adrian</p>
]]></description><link>https://community.m5stack.com/topic/8274/bottom2-and-m144-es8388-audio-module-i2s-bus-conflict</link><generator>RSS for Node</generator><lastBuildDate>Sat, 27 Jun 2026 20:10:16 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/8274.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 27 Jun 2026 13:53:20 GMT</pubDate><ttl>60</ttl></channel></rss>