Skip to main content
Visitor II
March 12, 2025
Solved

board resets continuously

  • March 12, 2025
  • 3 replies
  • 784 views

Hi, I am using the STM32F429ZI board. I enabled the hardware-independent watchdog timer using STM32CubeProgrammer option bytes. However, there are no errors or faults in my project—I have only enabled the GPIO and UART peripherals. But after enabling the hardware watchdog and performing a power-on reset, my board keeps resetting continuously.

On the other hand, when I enabled the software-independent watchdog timer using firmware, the board did not reset. Why is this issue occurring only with the hardware watchdog timer?

I also tried refreshing the IWDG after enabling the hardware-independent watchdog timer, but it still keeps resetting my board.

    This topic has been closed for replies.
    Best answer by mƎALLEm

    @Andrew Neil wrote:

    Are you sure that the reset is due to the watchdog?


    For that he needs to check the RCC_CSR register:

    mALLEm_0-1741778527710.png

    3 replies

    Technical Moderator
    March 12, 2025

    Hello,


    @kRaje.1 wrote:

    Hi, I am using the STM32F429ZI board.


    Sorry. STM32F429ZI is not a board but a MCU. Do you mean NUCLEO-F429ZI or 32F429IDISCOVERY?

    Super User
    March 12, 2025

    Are you sure that the reset is due to the watchdog?

    Are you sure that your code is correctly "kicking" the watchdog?

     


    @kRaje.1 wrote:

     there are no errors or faults in my project


    If you could be that certain, you wouldn't need a watchdog!

    mƎALLEmAnswer
    Technical Moderator
    March 12, 2025

    @Andrew Neil wrote:

    Are you sure that the reset is due to the watchdog?


    For that he needs to check the RCC_CSR register:

    mALLEm_0-1741778527710.png

    Super User
    March 12, 2025

    > Why is this issue occurring only with the hardware watchdog timer?

    There's a bug in the code where the watchdog isn't refreshed in time which causes the reset.

    Super User
    March 12, 2025

    @TDK wrote:

    > Why is this issue occurring only with the hardware watchdog timer?

    There's a bug in the code where the watchdog isn't refreshed in time which causes the reset.


    Or a design fault ...