Skip to main content
LCabé.1
LCabé.1
Associate
June 17, 2022
Solved

Program stuck in (Running : User Request) mode when using Debug from STM32CubeIDE

  • June 17, 2022
  • 2 replies
  • 3062 views

Hi,

I am using a microcontroller STM32L4R9AII6 on a STM32L4R9I-EVAL board, with IDE STM32CubeIDE (version 1.9.0)

I am trying to run a fairly simple code in Debug Mode, that just toggles a LED using some software overlay we developped.

It seems that after a determined number of instructions executed, the program get stuck in "Running : User Request" mode. (See picture error1)

I've noticed that my main while loop get executed everytime 18 times, and then the program get stuck.

I've tried adding somme dummy instructions inside the main while(1) loop, and the program then get stuck before (11 loop executions), 

as if a pre-determined maximum number of instructions could be ran.

The code that is being executed does not seem faulty at all, and have been running pretty well before.

When pressing "Suspend" once stuck in the "Running : Use Request", I get the error shown on picture "error2".

At this point I don't really know where to look and can't really explain anything of what is happening. It seems that there is no watchdog enabled, even though it seems that it might be some root cause here. (How could I double-check that ?)

Do you have any thoughts on where to look for ? Thanks in advance :)

Lilian

This topic has been closed for replies.
Best answer by Markus GIRDLAND

Hello Lilian,

I would start by setting a breakpoint and make sure you go through these 18 cycles (11 with dummy instructions) and then stepping to see exactly where things go wrong. You could even enable Instruction Stepping Mode to see which instruction is causing the issue. It might help you get to the bottom of what is happening.

0693W00000NsRjNQAV.png

2 replies

LCabé.1
LCabé.1Author
Associate
June 17, 2022

I also add that it seems that there is no watchdog enabled, even though it seems that it might be some root cause here. (How could I double-check that ?)

Markus GIRDLAND
Markus GIRDLANDAnswer
ST Employee
June 22, 2022

Hello Lilian,

I would start by setting a breakpoint and make sure you go through these 18 cycles (11 with dummy instructions) and then stepping to see exactly where things go wrong. You could even enable Instruction Stepping Mode to see which instruction is causing the issue. It might help you get to the bottom of what is happening.

0693W00000NsRjNQAV.png

Terms & ConditionsAccessibility statement