IMX WDT: Difference between revisions
No edit summary |
(Add Debian_Platform_Customization) |
||
Line 4: | Line 4: | ||
--> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!-- | --> {{#lst:Yocto_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!-- | ||
--> {{#lst:B2QT_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!-- | --> {{#lst:B2QT_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!-- | ||
--> {{#lst:Debian_Platform_Customization|{{#var:RELEASE_PARAM}}}} <!-- | |||
--> {{#ifexpr:{{#rpos:{{#var:SOC}}|mx8q}}<0| | --> {{#ifexpr:{{#rpos:{{#var:SOC}}|mx8q}}<0| | ||
{{#vardefine:WDT_CONFIG|CONFIG_IMX2_WDT}} | {{#vardefine:WDT_CONFIG|CONFIG_IMX2_WDT}} |
Revision as of 20:39, 7 February 2023
This page is using the default release RELEASE_SUMO_V1.0_VAR-SOM-MX6.
To view this page for a specific Variscite SoM and software release, please follow these steps:
- Visit variwiki.com
- Select your SoM
- Select the software release
Kernel configuration
The internal watchdog is enabled by default in the kernel configuration.
To verify that the i.MX watchdog driver (CONFIG_IMX2_WDT) is enabled in your kernel configuration:
- In menuconfig: Device Drivers -> Watchdog Timer Support -> <*> IMX2+ Watchdog
Using a command line
Watchdog will be activated as soon as /dev/watchdog is opened and will reboot unless the watchdog is pinged within timeout (128 is the preconfigured value).
# echo "1" > /dev/watchdog0
Within 128 seconds the board will reset.
Compile a watchdog test application
There's a watchdog testing utility C code example in the kernel source tree: tools/testing/selftests/watchdog-test.c (in older kernels: Documentation/watchdog/src/watchdog-test.c).
To cross compile it:
Install the toolchain and source the environment setup script, by following the Yocto Toolchain installation guide, then run:
$ $CC ./tools/testing/selftests/watchdog-test.c -o ./watchdog-test