cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with debugging & IWDG with STM32F407VGT6

Osto
Senior
Posted on September 21, 2016 at 15:56

Since firmware version 1.13 there is a big issue with debugging.

The firmware starts the watchdog during initialization. This result in reset when a breakpoint reaches. Before this version, I could start the IWDG by myselft to enable it.

Any Idea how to hint the firmware to start during initialization?

Or any Idea how to hint IWDG from run out during stop because of  breakpoint?

Thanks

Osto

2 REPLIES 2
Walid FTITI_O
Senior II
Posted on September 22, 2016 at 11:51

Hi

Osto

,

Overall rework of the IWDG driver in this version for a more efficient implementation

:

  • Remove the following APIs:

-

      

HAL_IWDG_Start()

-

      

HAL_IWDG_MspInit()

-

      

HAL_IWDG_GetState()

  • Update implementation:

-

      

HAL_IWDG_Init(): this function insures the configuration and the start of the IWDG counter

-

      

HAL_IWDG_Refresh(): this function insures the reload of the IWDG counter

Refer to drivers release note (in STM32Cube package ) for more details.

So,

HAL_IWDG_Init() in an old code, will start the IWDG.

-Hannibal-

Osto
Senior
Posted on September 27, 2016 at 14:09

Hi,

I solved the problem with __HAL_DBGMCU_FREEZE_IWDG() added in main.c after peripheral initialization.

In this case the WD-Counter will stop when debugger stops because of a breakpoint and hint to reset during the wait.

Thanks a lot,

Osto