High-resolution timer (HRTIM) RM0440
914/2126 RM0440 Rev 4
Master update caused by a
repetition event following a
roll-over
MSTU = 1 in
HRTIM_TIMxCR
MREPU = 1 in
HRTIM_MCR
Yes -
Master update caused by a
repetition event following a
counter reset (software or
due to HRTIM_SCIN)
No -
Software triggered master
timer update
MSTU = 1 in
HRTIM_TIMxCR
MSWU = 1
in HRTIM_CR2
No
All software update bits
(TxSWU) are grouped in the
HRTIM_CR2 register and can
be used for a simultaneous
update
TIMy update caused by a
TIMy counter roll-over
TyU = 1 in
HRTIM_TIMxCR
TyRSTU = 1 in
HRTIM_TIMyCR
Yes -
TIMy update caused by a
TIMy repetition event
TyU = 1 in
HRTIM_TIMxCR
TyREPU = 1 in
HRTIM_TIMyCR
Yes -
TIMy update caused by an
external event or a TIMy
compare (through a TIMy
reset)
TyU = 1 in
HRTIM_TIMxCR
TyRSTU = 1 in
HRTIM_TIMyCR
EXTEVNTn or
CMP4/2
in HRTIM_RSTyCR
Yes -
TIMy update caused by
sources other than those
listed above
TyU = 1 in
HRTIM_TIMxCR
No -
Repetition event following a
roll-over
TxREPU = 1 in
HRTIM_TIMxCR
Yes -
Repetition event following a
counter reset
No -
Timer reset
TxRSTU = 1 in
HRTIM_TIMxCR
No
Propagation would result in a
lock-up situation (reset causing
an update causing a reset)
Software
TxSWU in
HRTIM_CR2
No -
Table 230. Update event propagation for a timer reset (continued)
Source Condition Propagation Comment