STM32L4P5RG debugging in low power mode
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-22 06:51 AM
I'm trying to debug the board based on STM32L4P5RG in low power mode using the SEGGER tools (J-Link, RTT viewer, SystemView)
The device enters the low power mode periodically using the call
HAL_PWR_EnterSTOPMode(PWR_LOWPOWERREGULATOR_ON, PWR_STOPENTRY_WFI);
I also enable the the low power mode debug by caling HAL_DBGMCU_EnableDBGStopMode()
So far I see that the debug tools misbehave. For example the RTT viewer capture of printouts corrupts upon first entry to the STOP mode and does not come back.
When looking at the SEGGER forum I found that in order for debug tools to operate, the debug module shall be able to access the RAM (that probably fails in my case).
They recommend to confirm with the uCU vendor if the RAM access in low power mode is possible (bus clock on??) for the specific device. Can you please comment on this?
Solved! Go to Solution.
- Labels:
-
STM32L4 Series
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-22 10:30 AM
The alternative is to come up with other ways to understand how your own code is behaving.
Up vote any posts that you find helpful, it shows what's working..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-12-22 10:30 AM
The alternative is to come up with other ways to understand how your own code is behaving.
Up vote any posts that you find helpful, it shows what's working..
