|
157 | 157 | * Makefile add: |
158 | 158 | * |
159 | 159 | * ~~~~~~~~~~~~~~~~~~~~~~~~ {.mk} |
160 | | - * MODULE += periph_wdt_cb |
| 160 | + * USEMODULE += periph_wdt_cb |
161 | 161 | * ~~~~~~~~~~~~~~~~~~~~~~~~ |
162 | 162 | * |
| 163 | + * WDT Auto-Start |
| 164 | + * ============== |
| 165 | + * |
| 166 | + * It is possible to enable the Watchdog in early boot, before application startup: |
| 167 | + * |
| 168 | + * ~~~~~~~~~~~~~~~~~~~~~~~~ {.mk} |
| 169 | + * USEMODULE += periph_wdt_auto_start |
| 170 | + * ~~~~~~~~~~~~~~~~~~~~~~~~ |
| 171 | + * |
| 172 | + * The watchdog will automatically be initialized with the parameters |
| 173 | + * @ref CONFIG_PERIPH_WDT_WIN_MIN_MS and @ref CONFIG_PERIPH_WDT_WIN_MAX_MS |
| 174 | + * |
| 175 | + * It is also possible to automatically kick the watchdog. |
| 176 | + * This is a very non-invasive way of using the watchdog, but it is also very |
| 177 | + * weak as it can only detect situations where low-priority threads are |
| 178 | + * starved from execution and may even trigger wrongly in situations where the |
| 179 | + * system just experiences high load, but would otherwise have recovered on it's own. |
| 180 | + * |
| 181 | + * If you want to enable it anyway, select this module: |
| 182 | + * |
| 183 | + * ~~~~~~~~~~~~~~~~~~~~~~~~ {.mk} |
| 184 | + * USEMODULE += auto_init_wdt_thread |
| 185 | + * ~~~~~~~~~~~~~~~~~~~~~~~~ |
| 186 | + * |
| 187 | + * If you are using an event thread, you can also use the watchdog to ensure that events |
| 188 | + * are processed in time. |
| 189 | + * To do so, add |
| 190 | + * |
| 191 | + * ~~~~~~~~~~~~~~~~~~~~~~~~ {.mk} |
| 192 | + * USEMODULE += auto_init_wdt_event |
| 193 | + * ~~~~~~~~~~~~~~~~~~~~~~~~ |
| 194 | + * |
| 195 | + * |
163 | 196 | * @{ |
164 | 197 | * |
165 | 198 | * @file wdt.h |
|
0 commit comments