watchdog     ( -- )        Activate watchdog
watchdog?    ( -- flag )   Has the WATCHDOG bitten?
watchdog#    ( -- u )      How many times has the watchdog bitten since cold startup?

If thread takes longer than about 500 ms the watchdog will bite and a reset occurs. As long the thread waits for an event e.g. file operation, keyboard (the thread is blocked), nothing happens.

: forever begin again ; [RET] ok.
watchdog? .[RET] 0  ok.
watchdog[RET]  ok.
forever[RET] BOOM
Mecrisp-Stellaris RA 2.5.4 by Matthias Koch.

Mecrisp-Cube 1.4.4 for STM32WB55, 63/128 KiB RAM/FLASH dictionary (C) 2021 peter@spyr.ch
  * Firmware Package STM32Cube FW_WB V1.11.0, USB-CDC, BLE Stack 5.0 (C) 2021 STMicroelectronics
  * CMSIS-RTOS V2 FreeRTOS wrapper, FreeRTOS Kernel V10.3.1 (C) 2020 Amazon.com
  * FatFs for internal flash and microSD - Generic FAT fs module  R0.12c (C) 2017 ChaN
  * tiny vi - part of BusyBox (C) 2000, 2001 Sterling Huxley

watchdog? .[RET] -1  ok.
watchdog# .[RET] 1  ok.

Do not activate the watchdog in debugging mode.

watchdog? [IF] .( Watchdog has bitten, # bites: ) watchdog# . cr [THEN]

Implementation

For STM32WB55:

WWDG clock (Hz) = PCLK1 / (4096 * Prescaler)

PCLK1 is 32 MHz, Prescaler is 64, 
clock = 32 MHz / (4096 * 64) = 122 Hz

WWDG timeout (mS) = 1000 * (T[5;0] + 1) / WWDG clock (Hz)

timeout = 1000 * 64 / 122 = 524 ms
window  = 1000 * 48 / 122 = 393 ms

I choose 450 ms period to feed the watchdog.

• https://github.com/spyren/Mecrisp-Cube/blob/master/peripherals/watchdog.c
• https://github.com/spyren/Mecrisp-Cube/blob/master/peripherals/watchdog.h
• https://github.com/spyren/Mecrisp-Cube/blob/master/Core/Src/wwdg.c
• https://github.com/spyren/Mecrisp-Cube/blob/master/peripherals/clock.h

Watchdog

Intro

For serious real time systems you need a watchdog to detect and recover from malfunctions e.g. deadlocks. STM32 MCUs have two of them: independent watchdog (IWDG) and window watchdog (WWDG). I prefer the WWDG because it has a time window (as the name implies) and an interrupt just before the watchdog is going to bite. Window means that the feeding time has to be in a time window (interval), to feed to early is harmful too. The early wakeup interrupt can be used to bring the system into a save state or log something before the CPU is going into reset.

I create a thread only to kicking (regularly feed) the watchdog. This thread has the second lowest priority (just higher than the idle thread), if any task does not want to give up control, the watchdog thread does not get any more CPU time and cannot feed the watchdog and the watchdog bites.

Contents

• How to use
• Implementation

How to use

How to Create a Thread

-- Peter Schmid - 2021-12-25

This work by Peter Schmid is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.