2024-10-25 06:58 AM - edited 2024-10-25 07:02 AM
I am working with STM32 U575/U5A5 series of STM32 controllers in low power mode. I have programmed the controller to enter into Stop 3 mode and wake from stop3 mode based on wakeup Pin(High on PF2). With this implementation issue what we observed is once immediately flashing hex file into controller using STlink programmer, Controller is entering in stop3 mode but it is not waking up from stop3 mode even after low to high transistion on wakeUp pin(PF2). If I remove the power and connect it back, it is working as expected enterning into stop mode 3 and waking up from stop mode 3 on low to high transistion on wakeUp pin(PF2) all the time.
The question here is why for the first time after flashing hex file into controller, entering into stop3 mode but not waking up from stop3 mode and requires power reset?
low power mode is configured as follows:
Solved! Go to Solution.
2025-01-20 02:31 AM
Hello everyone,
I’ve moved the last comment of @mohan-ltts which wasn’t directly related to the initial post (Separate thread link: Issue to wake up from stop 3 mode when migrating fr... - STMicroelectronics Community)
However, to conclude this discussion, the issue is resolved when suspending SysTick before entering stop 3 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-02-20 09:39 PM
Hello,
I continued further checking. Tried things as suggested by ST team in forum (i.e. checking with LPMODE_RTC code and ST cube examples). Herewith few observations. Some of the observation are little different than earlier reported.
I use ST Cube programmer for board flashing. After flashing the code I keep it connected.
In the example code (modified), when MCU enters in to STOP 3 mode, ST cube programmer connection gets disconnected.
I don't see same behavior (i.e. ST cube programmer connection break) with older code base and ST Cube low power sample code.
Behavior with 2.17 cube programmer and earlier one is same. It seems to me issue it is not ST cube programmer related.
Then I modified firmware to make it enter in to STOP 2 mode (instead of STOP 3), it works fine as expected i.e. MCU is coming out of sleep mode on system reset and RTC timeout.
Note: As reported at start of the thread this issue is occurring only first time after flash programming.
Wondering in new code base when MCU enters in to STOP 3 mode is connection break with ST cube programmer is acceptable behavior or not. If it is not then does it give any clue what could be wrong with new code base as same thing is not happening with older code base and with ST cube example.
Please let me know if any additional details are needed. Appreciate for any inputs which could help for debugging further. Thank you.