Quicklogic Forums

Hi everyone, I’m working with the EOS-S3 and trying to wake the chip from deep sleep using a GPIO interrupt (rising edge). The device enters deep sleep correctly, but it doesn’t wake up when the GPIO signal changes, even though the same pin works fine in normal sleep mode. I’ve already enabled the GPIO interrupt and checked pull-up/down settings. Is there any EOS-S3–specific configuration or limitation for GPIO-based wake-up from deep sleep that I might be missing?

annasm wrote: ↑Mon Jan 05, 2026 6:45 am Hi everyone, I’m working with the EOS-S3 and trying to wake the chip from deep sleep using a GPIO interrupt (rising edge). The device enters deep sleep correctly, but it doesn’t wake up when the GPIO signal changes, even though the same pin works fine in normal sleep mode. I’ve already enabled the GPIO interrupt and checked pull-up/down settings. Is there any EOS-S3–specific configuration or limitation for GPIO-based wake-up from deep sleep that I might be missing? drift boss

In deep sleep, not all GPIOs can act as wake sources on the EOS-S3. Make sure the pin is supported for deep-sleep wake and enabled in the low-power/wake configuration (not just as a normal GPIO interrupt). Also check whether deep sleep requires level-triggered wake instead of edge-triggered.
The power management section of the reference manual should list the valid wake pins and limits.

Experiencing EOS-S3 deep sleep wake-up issues via GPIO? Many developers face similar challenges. Debugging requires careful attention to pin configurations and power management settings.

annasm wrote: ↑Mon Jan 05, 2026 6:45 am Hi everyone, I’m working with the EOS-S3 and trying to wake the chip from deep sleep using a GPIO interrupt (rising edge). The device enters deep sleep correctly, but it doesn’t wake up when the GPIO signal changes, even though the same pin works fine in normal sleep mode. I’ve already enabled the GPIO interrupt and checked pull-up/down settings. Is there any EOS-S3–specific configuration or limitation for GPIO-based wake-up from deep sleep that I might be missing?

Check if your SDK (QuickLogic Open Source SDK / SensiML / Zephyr port, etc.) provides helper functions like pmu_enable_gpio_wakeup(), wake_from_deep_sleep_on_gpio(), or similar.

wornouthos wrote: ↑Wed Apr 08, 2026 9:19 am

annasm wrote: ↑Mon Jan 05, 2026 6:45 am Hi everyone, I’m working with the EOS-S3 and trying to wake the chip from deep sleep using a GPIO interrupt (rising edge). The device enters deep sleep correctly, but it doesn’t wake up when the GPIO signal changes, even though the same pin works fine in normal sleep mode. I’ve already enabled the GPIO interrupt and checked pull-up/down settings. Is there any EOS-S3–specific configuration or limitation for GPIO-based wake-up from deep sleep that I might be missing?

Check if your SDK (QuickLogic Open Source SDK / SensiML / Zephyr port, etc.) provides helper functions like pmu_enable_gpio_wakeup(), wake_from_deep_sleep_on_gpio(), or similar.

Hello, I checked it, but it still isn't working. Are there any other solutions?

Exploring the concept of curve rush deeply resonates with how we approach performance optimization today. Perhaps integrating user feedback could enhance our understanding further—collective insights often drive innovation!
curve rush game

annasm wrote: ↑Mon Jan 05, 2026 6:45 am Hi everyone, I’m working with the EOS-S3 and trying to wake the chip from deep sleep using a GPIO interrupt (rising edge). The device enters deep sleep correctly, but it doesn’t wake up when the GPIO signal changes, even though the same pin works fine in normal sleep mode. I’ve already enabled the GPIO interrupt and checked pull-up/down settings. Is there any EOS-S3–specific configuration or limitation for GPIO-based wake-up from deep sleep that I might be missing?best sex dolls

My suspicion is that the GPIO interrupt is configured correctly for sleep mode, but the GPIO has not been registered with the deep-sleep wake-up controller or that particular GPIO is not available as a deep-sleep wake source.

I've tested this solution, and it seems quite promising.
moto x3m

I faced a similar issue with deep sleep GPIO wake-ups on my EOS-S3 project last year. The problem was that I needed to explicitly configure the interrupt as a wake-up source before entering deep sleep—just enabling GPIO interrupts wasn't enough. I found that testing my response times with a Cps Test platform helped me verify the actual wake-up latency and confirm the configuration worked. Make sure your deep sleep entry function includes the wake-up source registration, and double-check the power domain settings for that GPIO pin in your chip's datasheet.