Problems with sleep mode

[VicSF]

Hi,
We’re working on BG95-M3 running QuecPython and are trying to achieve low power consumption (sleep mode). However, we’ve noticed that the module remains in idle mode (~5 mA) and never reaches true low power (~0.5 mA) as long as any peripheral (I2C, SPI, UART) is initialized even if there’s no activity on the bus.

We tried using the .close() methods, but when we try to use the peripherals again, the module resets by itself. We also tried closing the peripherals and reinitializing them when needed, but it always causes a reboot.

How can we enter sleep mode without deinitializing the peripherals?

BR

[Felix.feng-Q]

@VicSF

We’re working on BG95-M3 running QuecPython and are trying to achieve low power consumption (sleep mode). However, we’ve noticed that the module remains in idle mode (~5 mA) and never reaches true low power (~0.5 mA) as long as any peripheral (I2C, SPI, UART) is initialized even if there’s no activity on the bus.

We tried using the .close() methods, but when we try to use the peripherals again, the module resets by itself. We also tried closing the peripherals and reinitializing them when needed, but it always causes a reboot.

How can we enter sleep mode without deinitializing the peripherals?

hi，VicSF

May I ask if the tasks are in a blocked state before entering low-power mode? And has the USB connection been disconnected? Generally, after configuring pm.autosleep(1) , the module will automatically enter sleep mode when all tasks are blocked (e.g., waiting for a semphore or in a sleep delay) and the USB is disconnected.