2025-07-20 11:57 PM - last edited on 2025-07-21 1:57 AM by Andrew Neil
Hi everyone , I'm testing ultra-low power on the NUCLEO-WL55JC using STM32CubeIDE . My goal is to reach ~0.9 µA in Stop 2 mode, but I consistently measure around 2.9 mA, even with the debugger disconnected. My setup: Stop 2 mode enabled MSI @ 100 kHz, PLL disabled PVD disabled All unused GPIOs set to analog SUBGHZSPI clock disabled Debug disabled CPU2 not activated Tick suspended Entering Stop 2 with HAL_PWREx_EnterSTOP2Mode() Measurement: JP7 and JP8 removed Powered via JP1 using STLINK-V3PWR Measured with STM32CubeMonitor-Power Question: Why is the current still so high? Is there anything specific on the NUCLEO-WL55JC board (RF switch, etc.) that needs to be disabled? Any working CubeIDE example that reaches ~0.9 µA?
Solved! Go to Solution.
2025-08-25 3:02 AM
Hey @marouax,
>>is there anything specific on the NUCLEO-WL55JC board (RF switch, etc.) that needs to be disabled?
RF switch can consume ~30 µA, also disable components like VDDRF, VDDRF1V5, VDDPA, VDDA, and VDDREF+.
This also could be related to power flags not being cleared before entering Stop2 mode.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-08-18 2:25 AM
Hello @marouax,
I'm not sure you are even entering stop2 mode with this current consumption, could you share the sequence to enter stop2 mode? Also, what's your wakeup source?
Could you try running this example from the STM32CubeWL
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-08-21 12:28 AM
Hello @Sarra.S,
Thanks for your feedback. You’re right, I might not be entering Stop2 mode correctly. My wakeup source is the RTC, and I’ve been following a custom sequence. I’ll try running the STM32CubeWL example you mentioned to check the behavior and compare the current consumption with mine. Also
I’m testing the End Node application on the NUCLEO-WL55JC1, but the RF pins are shown in pink (not activated). Also, when I generate code, I get this message: Main Config: These peripherals still have some not configured or wrong parameter values: [LORAWAN, Verify the Platform Settings Tab , STMicroelectronics.X-CUBE-MEMS1.11.3.0, Verify the Platform Settings Tab ]. The application doesn’t work. Any idea how to solve this?
Thanks in advance.
2025-08-25 3:02 AM
Hey @marouax,
>>is there anything specific on the NUCLEO-WL55JC board (RF switch, etc.) that needs to be disabled?
RF switch can consume ~30 µA, also disable components like VDDRF, VDDRF1V5, VDDPA, VDDA, and VDDREF+.
This also could be related to power flags not being cleared before entering Stop2 mode.
To give better visibility on the answered topics, please click on Accept as Solution on the reply which solved your issue or answered your question.
2025-08-25 7:07 AM
In this project, I successfully tested the Stop Mode on the NUCLEO-WL55JC1, and the functionality worked as expected. However, when I attempted to extend the work towards radio communication (LoRaWAN), I encountered blocking issues. Specifically, while testing the End Node application, the RF pins appeared in pink (inactive) in CubeMX, and during code generation the following error message was displayed:
Main Config: These peripherals still have some not configured or wrong parameter values: [LORAWAN, Verify the Platform Settings Tab , STMicroelectronics.X-CUBE-MEMS1.11.3.0, Verify the Platform Settings Tab ]
As a result, the radio part of the application could not be tested. Another limitation of this work was the unavailability of a LoRa gateway, which prevented me from verifying a complete end-to-end communication setup.
I already sent you the picture of the error. The application still doesn’t work. Do you have any idea how to solve this?