fs23 wdg questions

[gumu]

Hello,

we are currently debugging the FS23 and would like to ask a question about the watchdog: By default, can the watchdog be permanently disabled through software? Is it done by setting the window to infinite? If it can be disabled, but I saw in the chip manual that it states:

“At power-on reset, the first good watchdog refresh must be sent in less than 256 ms, which is the default watchdog period. If not, the watchdog error counter will be incremented (see section 20.2.2 Watchdog error counter). ”

This mentions that after POR, the watchdog must be refreshed correctly within 256 ms; if the watchdog is disabled, then this 256 ms timeout becomes meaningless, right?

[TomasVaverka]

Hi,

The watchdog disable (WDW_PERIOD = 0b0000) is effective only when the INIT phase is closed, so it requires at least one good watchdog refresh within the 256ms of the INIT timeout.

BRs, Tomas

[gumu]

Hi @TomasVaverka 

The manual describes: "At power-on reset, the first successful watchdog refresh must be sent within less than 256 ms, which is the default watchdog period. If not, the watchdog error counter will be incremented (see section 20.2.2 Watchdog error counter)." 

Based on this description, I conducted an experiment where after the system is powered on, I did not execute the wd refresh and observed how long it would take for the system to reset. My code was similar to this:

Std_ReturnType Sbc_fs23_WdRefresh(void) 
{ 
    Std_ReturnType eReturnValue = E_OK; 
    uint16 u16WdToken = 0U; 
    while(1); 
......
do not do any code
......
}

 Through monitoring the device reset, I found that it reset after approximately 850ms. Why is it not 256ms but 850ms?What FS23 factors are related to device reboot?

below is the waveform I measured, the green line is level of reset pin.

gumu_0-1731235658734.png

Thanks!

[TomasVaverka]

Hi,

Each time the watchdog is not properly refreshed, the watchdog error counter is incremented by 2. When is reaches its configurable limit (6 by default), the fault error counter is incremented by 1 and the RSTB is asserted (WD_RSTB_IMPACT = 1 by default). This corresponds to 3 * 256ms = 768ms.

1.png

2.png

3.png

BRs, Tomas

[gumu]

Hi @TomasVaverka ,

Thank you for your support!

I would like to ask, in your explanation, 'This corresponds to 3 * 256ms = 768ms.' In the init state, the default timeout is 256ms, but the watchdog timeout period is 64ms. If the watchdog is not correctly refreshed during the init state, is 256ms considered the watchdog timeout period?

Tnanks!

[TomasVaverka · Accepted solution]

Hi,

If you change the watchdog window period from the default value of 256ms to 64ms ((WDW_PERIOD = 0b0011)) during the INIT phase, and the watchdog is not correctly refreshed during the 256ms INIT phase, then the watchdog window period remains 256ms.

Screenshot 2024-11-11 133131.png

BRs, Tomas

[gumu]

Hi Tomas,

Thank you for your answer!

After the system powers on and enters the INIT state, if the watchdog is set to infinite during the INIT state and then a good watchdog refresh is performed to exit the INIT state, does that mean the watchdog is effectively disabled? If my understanding is correct, how does the FS23 exit the infinite mode? Is it through the Sbc_fs23_WdChangeWindowDuration() interface?

Thanks!

[gumu]

I’ve encountered a phenomenon where, after powering on the system, it does not restart even if the watchdog is not refreshed. Therefore, I think it may be due to the FS23 disabling the watchdog during initialization. However, I do not fully understand the details regarding how to disable the watchdog.

[TomasVaverka]

Hi,

I suppose that in this case the FS23 is in Debug mode (VDBG > VDBG_MODE (min: 3.5V; typ: 4.5V; max: 5.5V)) where no watchdog refresh is required as the watchdog is configured with infinite timeout and the watchdog window is fully opened. Also the RSTB eight-second timer is disabled and the Fail-safe mode entry is disabled via the fault error counter.

BRs, Tomas