Date: Thu, 7 Nov 2013 00:04:33 +0800 From: Jia-Shiun Li <jiashiun@gmail.com> To: Oleksandr Tymoshenko <gonzo@bluezbox.com> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, Andreas Schwarz <freebsd.asc@strcmp.org> Subject: Re: raspberry pi BCM2708 hardware watchdog Message-ID: <CAHNYxxOzi-xFksrBtzr4m-A2WVaGkf5aakGNzUMKvGMQ2DVKcw@mail.gmail.com> In-Reply-To: <CAHNYxxM8MYZRBFvf3cSGB=MOM-CLMOwudJMWdzb-UwAvXK4r%2Bg@mail.gmail.com> References: <43584768717.406e8ebb@mail.schwarzes.net> <F4029D36-8C55-4617-A429-0C5A3DA31C63@bluezbox.com> <CAHNYxxM8MYZRBFvf3cSGB=MOM-CLMOwudJMWdzb-UwAvXK4r%2Bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 1, 2013 at 3:11 AM, Jia-Shiun Li <jiashiun@gmail.com> wrote: > I tried playing the watchdog for a while, but it does not seem to be > set correct timeout. > > I tried to set timeout to 120 seconds to test with the following > command, but get immediate reset after around 1~2 seconds: > Just found out that - watchdog(4) uses 2^N ns format for timeout value, and - watchdog timeout value on BCM2835 is restricted to < 16 secs due to register constraint so for watchdog(d) users the only meaningful -t value on RPi is 1, 2, 4, and 8 seconds. In case others may have the same question. -Jia-Shiun.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHNYxxOzi-xFksrBtzr4m-A2WVaGkf5aakGNzUMKvGMQ2DVKcw>