Skip to main content
Associate
March 6, 2024
Solved

HRTIM Setting BUG?

  • March 6, 2024
  • 1 reply
  • 2312 views

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.

 

ink_0-1709708414469.png

    This topic has been closed for replies.
    Best answer by Ghofrane GSOURI

    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

    1 reply

    Ghofrane GSOURI
    Technical Moderator
    March 6, 2024

    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 

    GhofraneGSOURI_1-1709716554762.png

     

    Thx

    Ghofrane

    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.
    inkAuthor
    Associate
    March 6, 2024

    hello, Ghofrane
    Thank you Ripple.

     Did you set up deadtime insertion?

    Insert Deadtime: Insert deadtime between output 1 and output 2.

    ink_0-1709717594958.png

     

    Ghofrane GSOURI
    Ghofrane GSOURIBest answer
    Technical Moderator
    March 6, 2024

    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

    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.