<?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[Unable to wake M5StickC using SH200Q&#x27;s activity interrupt]]></title><description><![CDATA[<p dir="auto">According to some of the documentation (and a random issue on GitHub), the SH200Q should be hooked up to GPIO35 to wake the stick from deep sleep upon activity. While running, I can see this interrupt being triggered, but it never actually wakes from deep sleep.</p>
<p dir="auto">Here's the code I use to set up the interrupt:</p>
<pre><code>// Enable acc interrupt
  buf = 1&lt;&lt;1;
  M5.IMU.I2C_Write_NBytes(SH200I_ADDRESS, 0x14, 1, &amp;buf);

  // Set acc threshold
  buf = 100;
  M5.IMU.I2C_Write_NBytes(SH200I_ADDRESS, 0x17, 1, &amp;buf);
  
  // Set amount of time acc must be in threshold before interrupt is triggered
  buf = 4;
  M5.IMU.I2C_Write_NBytes(SH200I_ADDRESS, 0x19, 1, &amp;buf);

  // set gyro x/y/z as inputs for interrupt (bit 7 enables the use of TIME_THRESHOLD)
  buf = 1&lt;&lt;4 | 1&lt;&lt;5 | 1&lt;&lt;6 | 1&lt;&lt;7;
  M5.IMU.I2C_Write_NBytes(SH200I_ADDRESS, 0x1B, 1, &amp;buf);
</code></pre>
<p dir="auto">And this is the line that should enable wake on GPIO35 activity:<br />
<code>esp_sleep_enable_ext0_wakeup((gpio_num_t)35, 1); // set ext0 to wake up when GPIO35 is high</code></p>
<p dir="auto">I've also tried enabling wakeup on one of the external M5Stick buttons as a sanity check.. that worked fine.</p>
<p dir="auto">My question; is the SH200Q's interrupt actually hooked up to anything, and if so what? Or is there some error in my code?</p>
]]></description><link>https://community.m5stack.com/topic/1400/unable-to-wake-m5stickc-using-sh200q-s-activity-interrupt</link><generator>RSS for Node</generator><lastBuildDate>Tue, 28 Apr 2026 20:43:29 GMT</lastBuildDate><atom:link href="https://community.m5stack.com/topic/1400.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 16 Oct 2019 22:46:15 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Unable to wake M5StickC using SH200Q&#x27;s activity interrupt on Wed, 01 Jul 2020 21:02:42 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/marsalkm" aria-label="Profile: marsalkm">@<bdi>marsalkm</bdi></a> This ability should work on M5StickC units with the MPU6886. There's more info on this thread here:<br />
<a href="https://community.m5stack.com/topic/2039/wake-up-on-pick-up">https://community.m5stack.com/topic/2039/wake-up-on-pick-up</a></p>
]]></description><link>https://community.m5stack.com/post/9223</link><guid isPermaLink="true">https://community.m5stack.com/post/9223</guid><dc:creator><![CDATA[davesee]]></dc:creator><pubDate>Wed, 01 Jul 2020 21:02:42 GMT</pubDate></item><item><title><![CDATA[Reply to Unable to wake M5StickC using SH200Q&#x27;s activity interrupt on Wed, 17 Jun 2020 17:21:03 GMT]]></title><description><![CDATA[<p dir="auto">Should this work when using the M5StickC model with the MPU6886 IMU?</p>
<p dir="auto">The schematic suggests that GPIO35 is wired to the external interrupt of the MPU6886 <a href="https://docs.m5stack.com/#/en/core/m5stickc" target="_blank" rel="noopener noreferrer nofollow ugc">https://docs.m5stack.com/#/en/core/m5stickc</a></p>
<p dir="auto">Cheers,<br />
Dave</p>
]]></description><link>https://community.m5stack.com/post/9036</link><guid isPermaLink="true">https://community.m5stack.com/post/9036</guid><dc:creator><![CDATA[davesee]]></dc:creator><pubDate>Wed, 17 Jun 2020 17:21:03 GMT</pubDate></item><item><title><![CDATA[Reply to Unable to wake M5StickC using SH200Q&#x27;s activity interrupt on Mon, 28 Oct 2019 02:57:33 GMT]]></title><description><![CDATA[<p dir="auto">IMU does not control GPIO35 to issue an interrupt</p>
]]></description><link>https://community.m5stack.com/post/6186</link><guid isPermaLink="true">https://community.m5stack.com/post/6186</guid><dc:creator><![CDATA[vany5921]]></dc:creator><pubDate>Mon, 28 Oct 2019 02:57:33 GMT</pubDate></item></channel></rss>