I am using an STM32F103RB MCU in a specific Hardware design.
The Hardware was always working fine until I flashed a software which implements the stop mode (deep sleep mode) management (it's a low power mode supported by ST by setting the SLEEPDEEP bit in the System control register (SCB_SCR) supported by ARM).
In the Software after calling the set instruction WFI (wait for interrupt) to wait for an interrupt to wake-up the micro-controller, it still sleeping for ever.
In debug session (using j-link as debugger via SWD) by pressing next step in IAR, I can go out from deep sleep mode.
When I go out from debug session I can't connect anymore to the micro-controller and I can't flash it anymore.
I have the issue as described in the screenshot.
I am really stick with this and I look forward your help !
This is a question for ST and/or IAR - nothing to do with ARM
I guess it's related to the low-power mode management from ARM.
But anyway, it will help me if some one in the community can suggest any solution.
Thank you for your comprehension !
As you said yourself, it's ST's specific implementation - and that fact that it disables things like GPIO, etc.
So the ST forum would be the place to ask about that:
Or, if you want to know if IAR or Segger has any "special tricks" for escaping such situations - ask them.
Thank you Andy for your answer! I have already asked them.
Please post a link here - so that others can follow the full discussion.
I opened tickets in ST and Segger online support tools and posted in ST community. I can't post here links of several ongoing discussions.
But, I will share here the solution at the end.
Nidhal Ben Othmen said:I can't post here links of several ongoing discussions
Of course you can!
You should always do that when cross-posting the same question to multiple forums.
Okay, here are the posts in Segger forum and ST community
Sorry, for the tickets in online support, you will not have the access.But, I will share the result at the end!
Thank you Andy for your precision.
Have a nice day!
View all questions in Cortex-M / M-Profile forum