From: Felix Radensky <felix@embedded-sol.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2
Date: Thu, 03 Mar 2011 15:08:28 +0200 [thread overview]
Message-ID: <4D6F92CC.3010707@embedded-sol.com> (raw)
In-Reply-To: <4D6F8AB5.2050208@freescale.com>
Hi Timur,
On 03/03/2011 02:33 PM, Tabi Timur-B04825 wrote:
> Felix Radensky wrote:
>> Correct. It works fine in linux. I've even tried to port linux code that
>> enables watchdog (booke_wdt.c/__booke_wdt_enable()) to u-boot,
>> but was not successful. Watchdog never triggered, although I did
>> not refresh it.
>>
>> I'd appreciate some advice on what may be different in u-boot
>> vs. linux.
> I don't know what to tell you. I would need to try to make it myself in order to see what's going on. Maybe you really didn't program TCR correctly. Or maybe it is working, but the default behavior of U-Boot is to handle everything silently.
Thanks. I suspect u-boot WDT behaviour should be different from Linux.
Linux sets TCR_WIE bit to enable watchdog interrupt, u-boot should not
do this and just reset the CPU on first time-out. The TCR values are
identical
in u-boot and linux, except for TCR_WIE and TCR_DIE bits that are set
in linux.
Except not setting TCI_WIE bit and setting WRC to 10b, is there
anything else
that should be done to cause reset of first time-out ?
Felix.
next prev parent reply other threads:[~2011-03-03 13:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 0:10 [U-Boot] CONFIG_WATCHDOG on MPC85XX and QorIQ P1/P2 Felix Radensky
2011-03-03 4:18 ` Aggrwal Poonam-B10812
2011-03-03 4:20 ` Tabi Timur-B04825
2011-03-03 4:27 ` Dudhat Dipen-B09055
2011-03-03 7:41 ` Felix Radensky
2011-03-03 7:49 ` Albert ARIBAUD
2011-03-03 12:33 ` Tabi Timur-B04825
2011-03-03 13:08 ` Felix Radensky [this message]
2011-03-03 13:11 ` Tabi Timur-B04825
2011-03-07 9:38 ` Felix Radensky
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=4D6F92CC.3010707@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=u-boot@lists.denx.de \
/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