nrf54L15 power current question,on nordic Official test example bugs

[jhon0]

hello,https://github.com/NordicDeveloperAcademy/nrf54l-express/tree/main/demo_app/ The device draws 150 uA when powered on, and only after pressing button 3 can it properly switch between 1 uA power-off mode and 3 uA idle mode. Similarly, in C:\ncs\v3.2.4\nrf\samples\bluetooth\peripheral_power_profiling, it draws 150 uA when powered on and also requires calling the sys_poweroff function after 5 seconds to properly enter 1 uA mode. Why doesn't it directly enter 3 uA idle mode after power-on? The environment is 54L15 DK, ncs v3.2.4 ppk2. Thank you. PS: The peripheral_power_profiling demo works normally on the 52833 DK, entering 3 uA mode directly upon power-on.

[Edvin]

Hello,

I have not tested these samples directly, but it looks like the one that you link to first (DevAcademy), it seems like this should enter sleep. But I suspect that, the way you explain this, you see that the current consumption remains high after you program it, until it enters system-off mode, and then it starts in the low power mode after this.

I believe what you are seeing is that the device is in debug mode (150µA also supports this, that the HFCLK remains on). If you are testing different samples, remember to power cycle the device after you programmed it before you start measuring the current consumption, to make sure that you exit the debug mode. If you have logging enabled, opening an RTT viewer will also enable debug mode, causing increased current consumption. 

Best regards,

Edvin

[jhon0]

hello edvin, I haven't modified any code in these two official examples, and the phenomenon described above occurs. I've also pressed the RST reset button (with the debugger disconnected,and device is not in debug mode), but the behavior remains the same.

Thank you for your help.Are there any other possible causes? Thank you.Best regards