My application is using HRTIM in burst mode: PWM is generated part of the time by specifying a period and an idle/run duration based on common tick (TIMA counter).
Period (HRTIM_BMPER) is set once at init and idle duration (BMCMPR) updated every 20us. Sometimes I notice a period is empty of pulses while the application has never written max value in idle duration. It looks like it happens when idle duration is updated exactly at end of burst period. Next period contains correct number of pulses. 32-bit register write is atomic operation.
This bug is not visible when preload is used but if used system response is slower because idle duration is updated at end of burst period.
Can someone confirm this bug ?
Thanks,
Guillaume
