Skip to main content
Associate
February 26, 2026
Solved

STM32G474 HRTIMER Deadtime on skipped pulse.

  • February 26, 2026
  • 1 reply
  • 175 views

I've STM32G474 using the HRTIMER to control a boost converter, each channel has it's own converter. This all works nicely with the deadtime, no issues. When I come to do a pulse skip, (set CMP3 to 0) the deadtime is still being inserted in the the Tx2 output even though Tx1 output is not being pulsed! Is this normal or have I missed something?

I've tried a few things to not make the deadtime happen, like disabling the set and reset sources... the only thing that fixes the problem is to also set the falling deadtime to 0 and then subsequently resetting it back to the required value. Tx2 has no set or reset sources configured.

Best answer by jst-sention

Seems I have a misunderstanding of the Null duty cycle exception case, the manual states that the output set event can be the timer period and the reset event CMP1 or 3 but it looks like it is only the case when the timer runs in continuous mode. Output set on CMP1 and reset on CMP3 fixes the issue when in one shot mode.

1 reply

mƎALLEm
Technical Moderator
February 26, 2026

Hello @jst-sention and welcome to the ST community,

You need to provide more information about what you did at this level, share code etc ..

Please read How to write your question to maximize your chances to find a solution

Good luck

"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."
jst-sentionAuthorBest answer
Associate
February 26, 2026

Seems I have a misunderstanding of the Null duty cycle exception case, the manual states that the output set event can be the timer period and the reset event CMP1 or 3 but it looks like it is only the case when the timer runs in continuous mode. Output set on CMP1 and reset on CMP3 fixes the issue when in one shot mode.