Counter? Nucleo L476RG

[SWenn.1]

Can someone tell me when I use

uint16_t temp;
	temp = __HAL_TIM_GET_COUNTER(&htim2);

the above why temp doesn't equal the TIM2 CNT register in the debugger? I've also tried

temp = htim2.Instance->CNT;

[waclawek.jan]

> the above why temp doesn't equal the TIM2 CNT register in the debugger?

TIM2 running? temp was read out from TIM2 in a different time than when debugger read out TIM2_CNT register.

JW

[TDK]

Timers continue to run when execution is paused in the debugger by default. You can adjust that behavior in the DBGMCU freeze register settings.

[waclawek.jan]

> Timers continue to run when execution is paused in the debugger by default. You can adjust that behavior in the DBGMCU freeze register settings.

Even then, and even if you single-step, executing code which reads out TIMx_CNT may/will happen while the timer is running between steps, whereas the debugger reads it afterwards, so the values may/will differ.

JW

[SWenn.1]

being new to this tool suite can you point me to DBGMCU freeze settings location.....Somewhere under Properties- Run/Debug Settings?

[waclawek.jan · Accepted solution]

This is a normal peripheral register bit.

Maybe there's some setting to set these bits from inside the debugger, I don't know what debugger are you using.

JW

[SWenn.1]

Oh you are suggesting it is a bit in a register on the target? I thought it was a switch somewhere in the CubeMX IDE...

I am using ​a STLINK V3 SET

[TDK]

Yes, it is a bit within a register. Set it during startup of your program.
Note that you may still have a mismatch due to the registers being read at different times, but probably only a couple of counts. Debugging timers using single stepping through code is not ideal.

[SWenn.1]

Got it:thumbs_up:...will give it a try...

Thanks to all for the help​