1. The HRTIM FAULT function can only be triggered once, and reset by software after triggering. So is there any use of hardware periodic triggering (that is, reset immediately after triggering, similar to TripZone in C2000)? I want to use it as a cycle-by-cycle protection function.
2. CUBEMX enables Blanking by default when initializing HRTIM. I think it will cause misunderstanding?
Hello @ZZhu.1
First let me thank you for posting.
1-To achieve a cycle-by-cycle protection function, you would need to implement your own logic using the HRTIM's capture/compare features and interrupts.
You could set up a capture/compare unit to sample a specific signal or condition on each cycle and then use an interrupt to perform the necessary actions or trigger a fault if the condition exceeds a certain threshold.
This approach would require careful configuration and software implementation to achieve the desired functionality.
**Please check AN4539 paragraph 8.Cycle-by-cycle protection without deadtime insertion for more details and explanation .
2-Regarding the HRTIM initialization in CubeMX, the default configuration may indeed enable blanking.
Blanking is a feature that prevents certain events (such as fault events) from occurring immediately after a compare match. It provides a delay to avoid false triggering caused by transient effects.
While blanking can be useful in some applications, it might not be necessary or appropriate for all cases.
If you believe that blanking is causing misunderstanding or unwanted behavior in your application,
you can modify the HRTIM configuration in CubeMX to disable or adjust the blanking settings according to your requirements. By customizing the initialization code, you can ensure that the HRTIM operates as desired in your specific use case.
Thx
Ghofrane
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.