Watchdog - Revision history

JulienB: /* Usage */

2018-01-26T11:52:06Z

Usage

← Older revision		Revision as of 13:52, 26 January 2018
Line 34:		Line 34:
	</pre>		</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.		* 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}}		{{Note\|On [[APF27]] and [[APF51]] the watchdog is then unstoppable and will reset your board if you don't service it}}

2018-01-26T11:49:10Z

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

	== Links ==		== Links ==
	*		* https://www.kernel.org/doc/Documentation/watchdog/watchdog-api.txt

			[[Category:Watchdog]]

2018-01-26T11:47:25Z

Usage

← Older revision		Revision as of 13:47, 26 January 2018
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.		* 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}}		{{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):		* 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">		<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:		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">		<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>		</pre>

	== Links ==		== Links ==
	*		*

2018-01-26T11:45:46Z

Usage

← Older revision		Revision as of 13:45, 26 January 2018
Line 29:		Line 29:

	* Load the module if the watchdog is compiled as a module:		* 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">		<pre class="apf">
	# modprobe imx2-wdt timeout=5		# modprobe imx2-wdt timeout=5

2017-09-07T15:31:53Z

Installation

← Older revision		Revision as of 17:31, 7 September 2017
Line 18:		Line 18:

	== Installation ==		== 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.
			Otherwise either copy the generated module through NFS to your board or reflash your rootfs.

	== Usage ==		== Usage ==

2017-07-18T22:12:49Z

Usage

← Older revision		Revision as of 00:12, 19 July 2017
Line 33:		Line 33:
	</pre>		</pre>

	You can now access the watchdog through ''/dev/watchdog'' device file:		You can now access the watchdog through ''/dev/watchdog'' or ''/dev/watchdog0'' device file (depending on your board):
	* to activate it, just open the file, then you will have to write to this file regularly or your system will be reseted.		* 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}}		{{Note\|On [[APF27]] and [[APF51]] the watchdog is then unstoppable and will reset your board if you don't service it}}
Line 43:		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:		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">		<pre class="apf">
	# ~~killall~~ watchdog		# kill -19 PID (where PID is the one of watchdog process and -19 == SIGSTOP)
	</pre>		</pre>

	== Links ==		== Links ==
	*		*

2017-07-18T22:07:17Z

Usage

← Older revision		Revision as of 00:07, 19 July 2017
Line 23:		Line 23:
	== Usage ==		== Usage ==
	* If driver is statically linked to Linux, you can choose timeout value at boot time with:		* 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		BIOS> setenv extrabootargs imx2-wdt.timeout=5
	</pre>		</pre>

2017-07-18T22:07:01Z

Usage

← Older revision		Revision as of 00:07, 19 July 2017
Line 22:		Line 22:

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

	* Load the module if the watchdog is compiled as a module:		* 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]] the watchdog driver is compiled within the kernel and do not need to be loaded at runtime.}}
Line 32:		Line 37:
	{{Note\|On [[APF27]] and [[APF51]] the watchdog is then unstoppable and will reset your board if you don't service it}}		{{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 ~~the apf~~ board on timeout (here reset watchdog every 3 seconds and ask to reboot after 5s if not serviced):		* 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">		<pre class="apf">
	# watchdog -T 5 -t 3 /dev/watchdog		# watchdog -T 5 -t 3 /dev/watchdog

2013-09-04T15:56:23Z

Configuration

← Older revision		Revision as of 17:56, 4 September 2013
Line 5:		Line 5:
	First be sure to have the Watchdog Linux driver activated:		First be sure to have the Watchdog Linux driver activated:
	<pre class="host">		<pre class="host">
	$ make ~~linux26~~-menuconfig		$ make linux-menuconfig
	</pre>		</pre>

2012-07-11T06:20:35Z

Usage

← Older revision		Revision as of 08:20, 11 July 2012
Line 23:		Line 23:
	== Usage ==		== Usage ==
	* Load the module if the watchdog is compiled as a module:		* Load the module if the watchdog is compiled as a module:
	{{Note\|On [[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]] the watchdog driver is compiled within the kernel and do not need to be loaded at runtime.}}
	<pre class="apf">		<pre class="apf">
	# modprobe imx2-wdt timeout=5		# modprobe imx2-wdt timeout=5