From: Sascha Hauer <s.hauer@pengutronix.de>
To: Haris Papadopoulos <haris@amberbox.com>
Cc: barebox@lists.infradead.org
Subject: Re: How to configure Imx6ul watchdog from barebox
Date: Thu, 26 Jan 2017 08:39:33 +0100 [thread overview]
Message-ID: <20170126073933.sl5da36773g3misf@pengutronix.de> (raw)
In-Reply-To: <CACmkAZEckFyAA1zgS=j53RTMzqtxmwpiaNcHZ4=2jhA5uSKXJA@mail.gmail.com>
On Wed, Jan 25, 2017 at 07:27:01PM +0000, Haris Papadopoulos wrote:
> Hi,
>
> I am using barebox on a board from phytec phyBOARD-Segin that uses an
> imx6ul processor (phyCORE-i.MX 6UL).
>
> Any idea how to configure the watchdog to automatically start in the
> bootloader and then be kicked from linux? In which file do I have to
> do the following configs?
You can pass the -w option to the boot command, or, create a
nv.boot.watchdog_timeout variable (using nv boot.watchdog_timeout=10 for
example). This would enable the watchdog each time just before booting.
To enable/test the watchdog once you can use the 'wd' command. Use
'wd 3' to enable the watchdog with a timeout of three seconds and do
a 'wd 3' again before it runs out.
>
> CONFIG_WATCHDOG=y
> CONFIG_WATCHDOG_IMX=y
>
> Where can I setup the relevant flags?
>
> Also, does barebox have the bootcount feature?
I'm Not exactly sure where you aiming at. There is the bootchooser
framework which allows you to create different redundant boot scenarios
in which you can boot different systems based on successful/failed
booting combined with configurable watchdog timeouts. See
http://barebox.org/doc/latest/user/bootchooser.html
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-01-26 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 19:27 Haris Papadopoulos
2017-01-26 7:39 ` Sascha Hauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170126073933.sl5da36773g3misf@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=haris@amberbox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox