HRTIM Setting BUG?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-05 11:08 PM - edited ‎2024-03-05 11:14 PM
I am currently developing with the STM32G474 series, and there is a bug in the TIMER A setting of HRTIM.
To make OUTPUT1 and 2 differential outputs with dead time, enable SWAP OUTPUT.
If you set OUTPUT1's Source , Reset Source setting, cannot set the source and reset source of OUTPUT2.
However, Timer A cannot set the Set Source and Reset Source of OUTPUT2,
and the other Timer B, C, D, E, and F can set the Reset Source.
In fact, the reset source for OUTPUT2 must be set for the outputs to function properly.
Please fix so that the reset source of OUTPUT2 of Timer A can be set.
Solved! Go to Solution.
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-06 5:02 AM
Hello again @ink
Thank you for your contributions and for your detailed explanations
After double check , I confirm the issue on my side, it has been reported to STM32CubeMX development team .
Internal ticket number: 175381 (This is an internal tracking number and is not accessible or usable by customers).
I will keep you posted with updates.
Thx
Ghofrane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-06 1:16 AM
Hello @ink
First let me thank you for posting.
I tried to reproduce the issue using CubeMX 6.10.0 and everything works correctly please have a look
Thx
Ghofrane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-06 1:37 AM
hello, Ghofrane
Thank you Ripple.
Did you set up deadtime insertion?
Insert Deadtime: Insert deadtime between output 1 and output 2.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
‎2024-03-06 5:02 AM
Hello again @ink
Thank you for your contributions and for your detailed explanations
After double check , I confirm the issue on my side, it has been reported to STM32CubeMX development team .
Internal ticket number: 175381 (This is an internal tracking number and is not accessible or usable by customers).
I will keep you posted with updates.
Thx
Ghofrane
