Watchdog - Revision history

JulienB: /* Usage */

2018-01-26T11:52:06Z

‎Usage

2018-01-26T11:49:10Z

2018-01-26T11:47:25Z

‎Usage

2018-01-26T11:45:46Z

‎Usage

2017-09-07T15:31:53Z

‎Installation

2017-07-18T22:12:49Z

‎Usage

2017-07-18T22:07:17Z

‎Usage

2017-07-18T22:07:01Z

‎Usage

2013-09-04T15:56:23Z

‎Configuration

2012-07-11T06:20:35Z

‎Usage

@@ Line 34: / Line 34: @@
 </pre>
-You can now access the watchdog through ''/dev/watchdog'' or ''/dev/watchdog0'' device file (depending on your board):
+You can now access the watchdog through ''/dev/watchdog'' or ''/dev/watchdog0'' device file (depending on your board, ''/dev/watchdog'' might be the 1 minute software Linux watchdog):
 * to activate it, just open the file, then you will have to write to this file regularly or your system will be reseted.
 {{Note|On [[APF27]] and [[APF51]] the watchdog is then unstoppable and will reset your board if you don't service it}}

← Older revision		Revision as of 11:49, 26 January 2018
Line 47:		Line 47:

	== Links ==		== Links ==
−	*	+	* https://www.kernel.org/doc/Documentation/watchdog/watchdog-api.txt
		+
		+	[[Category:Watchdog]]

@@ Line 37: / Line 37: @@
 * to activate it, just open the file, then you will have to write to this file regularly or your system will be reseted.
 {{Note|On [[APF27]] and [[APF51]] the watchdog is then unstoppable and will reset your board if you don't service it}}
 * there is a small daemon useful to periodically trig the watchdog and reset or reboot your board on timeout (here reset watchdog every 3 seconds and ask to reboot after 5s if not serviced):
 <pre class="apf">
@@ Line 44: / Line 43: @@
 If your system hangs, the daemon can't trig the watchdog and your system is reseted. To quickly check that you can do a:
 <pre class="apf">
-  # kill -19 PID     (where PID is the one of watchdog process and -19 == SIGSTOP)
+  # kill -19 PID     (where PID is the one of watchdog process and -19 == SIGSTOP signal)
 </pre>
 == Links ==
+*

@@ Line 29: / Line 29: @@
 * Load the module if the watchdog is compiled as a module:
-{{Note|On  [[APF9328]]/[[APF27]]/[[APF28]]/[[APF51]] the watchdog driver is compiled within the kernel and do not need to be loaded at runtime.}}
+{{Note|On  [[APF9328]]/[[APF27]]/[[APF28]]/[[APF51]]/[[OPOS6UL]] the watchdog driver is compiled within the kernel and do not need to be loaded at runtime.}}
 <pre class="apf">
   # modprobe imx2-wdt timeout=5

@@ Line 18: / Line 18: @@
 == Installation ==
-If you choose to include driver in Linux kernel then reflash your kernel image.<br>
+If you choose to include driver in Linux kernel then reflash your kernel image.
-Else either copy the generated module through NFS to your board or reflash your rootfs.
 == Usage ==

@@ Line 23: / Line 23: @@
 == Usage ==
 * If driver is statically linked to Linux, you can choose timeout value at boot time with:
-<pre class="APF">
+<pre class="apf">
 BIOS> setenv extrabootargs imx2-wdt.timeout=5
 </pre>

@@ Line 5: / Line 5: @@
 First be sure to have the Watchdog Linux driver activated:
 <pre class="host">
-  $ make linux26-menuconfig
+  $ make linux-menuconfig
 </pre>