# M8108 problems with low power mode **URL:** \ **Category:** Software\ **Created:** [October 19, 2026, 2:15pm UTC](https://community.morsemicro.com/t/m8108-problems-with-low-power-mode/2107 "2026-10-19T14:15:42Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Roy](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@Roy](https://community.morsemicro.com/u/Roy)\ **Post date:** [October 19, 2026, 2:15pm UTC](https://community.morsemicro.com/t/m8108-problems-with-low-power-mode/2107/1 "2026-10-19T14:15:42Z")
We are using the M8108 on a custom PCB with a NXP RW612 as the main processor. The system is running Zephyr 4.4. I started with your MM-iot-sdk 2.10.4 porting it forward main involved handling recent MBEDTLS Zephyr changes. To get the M8108 to enter low power mode I had to turn on a pull-down on the Busy line. The application I am running will power up connect to the network, then a MQTT broker, and then publish JSON every 5 seconds. You can see the power and logic analyzer trace as it successfully completes 10 cycles. After which it fails to return to low power mode. The number of cycles it completes before failing varies. I have seen as many as 40. I can decode the SPI traffic if that would be helpful. The failure presents as WAKE and IRQ staying high. ![LogicAndPower](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/2X/4/40fe41cc8a5c1a1c488e8b87612c05b90ee8c0ec.png) ![MQTT_Traffic](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/2X/9/9c1843b5790c70710a92243aa4e9ac9f5eda697b.png) I am going to spend today working with your newer 2.13.1 release but I did not see anything in the release notes that seemed to describe what I am seeing. I would be happy to share schematics and layout information but not so publicly. * * * I just finished moving to the 2.13.1 SDK the behavior is largely the same. The power consumption profile seems to show a slight improvement at the beginning of the test as the module joins the network. Once it gets connected the behavior appears the same. It completed 17 wakeup, publish, and go back to sleep before it failed with the WAKE and IRQ lines high. ![image](https://us1.discourse-cdn.com/flex001/uploads/morsemicro/original/2X/5/5deb7120a0212d57fbcd61174db03cc2b560a733.png) ---
**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\ **Post date:** [October 19, 2026, 10:33pm UTC](https://community.morsemicro.com/t/m8108-problems-with-low-power-mode/2107/2 "2026-10-19T22:33:15Z")
Hey @Roy Have you had a look at [GitHub - MorseMicro/mm-iot-zephyr · GitHub](https://github.com/MorseMicro/mm-iot-zephyr), which is our Zephyr port of the MM IoT SDK. This might gove some insights into power consumption. On our reference platform (EKH05 we see an idle consumption current of ~150uA with the power management variant, and do not see the issue you’ve described. I have some power profile captures lying around which I can attach. ---
**Author:** ![Roy](https://avatars.discourse-cdn.com/v4/letter/r/4da419/32.png) [@Roy](https://community.morsemicro.com/u/Roy)\ **Post date:** [October 20, 2026, 6:45am UTC](https://community.morsemicro.com/t/m8108-problems-with-low-power-mode/2107/3 "2026-10-20T06:45:02Z")
Yes that is the code I started with. The first traces were done with version 2.10.4 and the second with 2.13.1. The MM8108 starts out entering and exiting low power mode as expected then fails. I have the SPI decoded if that would help. I have not found any documentation that explains the driver to MM8108 interactions. ---
**Author:** ![ajudge](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@ajudge](https://community.morsemicro.com/u/ajudge)\ **Post date:** [October 20, 2026, 4:20pm UTC](https://community.morsemicro.com/t/m8108-problems-with-low-power-mode/2107/4 "2026-10-20T16:20:41Z")
Please send the SPI traces through.