STM32WB5MMG does not respond to interrupt in low power mode and disabled debugger

[ljw]

I am using the STM32WB5MMG processor with SDK version 1.20.0. The basic operation involves periodically reading sensor data in response to interrupts generated by the sensor, and then transmitting this data via BLE. To reduce power consumption, we are utilizing low-power mode. With this setup, the overall functionality worked well.

However, when we tried to further reduce power consumption by changing CFG_DEBUGGER_SUPPORTED = 0, the device no longer seems to recognize interrupts from the sensor. Of course, reverting CFG_DEBUGGER_SUPPORTED = 1 resolves the issue, and the device operates without problems.

Have there been any reported instances of this kind of behavior? I'd appreciate any information you can provide regarding what to check or if there are any known solutions.

Best regards,

[STTwo-32]

Hello @ljw and welcome to the ST Community.

I think this post is discussing a similar behavior. It should help you.

Best Regards.

STTwo-32

[honista1]

Interesting issue! I’ve run into similar low-power mode challenges while optimizing APK  performance tracking for Honista.blog . In embedded systems or app frameworks, debugging behavior often changes once power-saving features kick in. Curious if enabling certain wake-up sources or tweaking sleep mode priorities helped you resolve it?