Radarcape:Watchdog: Difference between revisions

From Beast Wiki
Jump to navigation Jump to search
← Older editNewer edit →
imported>Dl4mea
imported>Beastadmin
No edit summary
Line 6: Line 6:
|}
|}


=Hardware Watchdog Retriggering=
=Hardware Watchdog Overview=


Starting with the 2nd production batch of the Radarcape, there is an external hardware watchdog foreseen. Due to the nature of the device, running 24/7 at various environmental conditions and remote locations, this extra safety is pretty useful. A MAX6371 device is beeing used for this, which needs to be retriggered once every minute on GPIO1_18. The first retrigger activity shall happen in the cape.sh shell skript as below, afterwards toggling GPIO1_18 should be done in the Linux application SW.
Starting with the 2nd production Batch, the Radarcape is equipped with a MAX6371 hardware watchdog. The hardware watchdog shall ensure that the Radarcape recovers if the system software hangs. This is especially important if the Radarcape is operated at remote locations.


It is expected that this retriggering is done in the Linux application software, but for testing it might be useful having a small command line retrigger:
The watchdog listens on GIPO_60 of the BeagleBone board for a toggling signal. If no toggling of the port happend, the BeagleBone board is being reset via the SYS_RESET pin. Therefore, GIPO_60 must be toggled by software at least once every minute otherwise the Radarcape reboots. Toggling of GIPO_60 is usually being done by the Radarcape daemon (rcd).


'''Linux 3.2 Versions'''
 
=Manual Hardware Watchdog Toggling=
 
In several circumstances it becomes necessary to temporarily stop or de-install the Radarcape daemon. It becomes necessary to toggle GIPO_60 to hinder the hardware watchdog rebooting the Radarcape. This can be achived using the following commands:


<source lang="bash">
<source lang="bash">
Line 26: Line 29:


<source lang="bash">while :; do echo 1 > /sys/class/gpio/gpio60/value; echo 0 > /sys/class/gpio/gpio60/value; echo 'Hit CTRL+C'; sleep 30; done</source>
<source lang="bash">while :; do echo 1 > /sys/class/gpio/gpio60/value; echo 0 > /sys/class/gpio/gpio60/value; echo 'Hit CTRL+C'; sleep 30; done</source>
'''Linux 3.8 Versions'''
todo

Revision as of 17:50, 6 July 2016

For Experts The tasks described in this manual require advanced knowledge of Unix/Linux.

Hardware Watchdog Overview

Starting with the 2nd production Batch, the Radarcape is equipped with a MAX6371 hardware watchdog. The hardware watchdog shall ensure that the Radarcape recovers if the system software hangs. This is especially important if the Radarcape is operated at remote locations.

The watchdog listens on GIPO_60 of the BeagleBone board for a toggling signal. If no toggling of the port happend, the BeagleBone board is being reset via the SYS_RESET pin. Therefore, GIPO_60 must be toggled by software at least once every minute otherwise the Radarcape reboots. Toggling of GIPO_60 is usually being done by the Radarcape daemon (rcd).


Manual Hardware Watchdog Toggling

In several circumstances it becomes necessary to temporarily stop or de-install the Radarcape daemon. It becomes necessary to toggle GIPO_60 to hinder the hardware watchdog rebooting the Radarcape. This can be achived using the following commands: 

echo *** Configure Watchdog retrigger pin & toggle first time
echo 07 > /sys/kernel/debug/omap_mux/gpmc_ben1
echo 60 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio60/direction
echo 1 > /sys/class/gpio/gpio60/value
echo 0 > /sys/class/gpio/gpio60/value

A single line retrigger command looks like: 

while :; do echo 1 > /sys/class/gpio/gpio60/value; echo 0 > /sys/class/gpio/gpio60/value; echo 'Hit CTRL+C'; sleep 30; done
Retrieved from "https://wiki.jetvision.de/index.php?title=Radarcape:Watchdog&oldid=2488"