From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Watchdog support for ppc4xx
Date: Thu, 20 May 2010 13:55:01 +0200 [thread overview]
Message-ID: <201005201355.01964.sr@denx.de> (raw)
In-Reply-To: <B02FCC6065C3164C8228CF04AB049EAC010CBC91@srv-01.aplabs.com>
Hi Mark,
On Thursday 20 May 2010 00:27:50 Mark Maestas wrote:
> I have a question about watchdog support for PPC_4xx. When I define
> CONFIG_WATCHDOG in canyonlands.h, I get an error when building
> cpu_init.c. The error code reads:
>
> {standard input}: Assembler messages:
> {standard input}:133: Error: unsupported relocation against tcr
> {standard input}:141: Error: unsupported relocation against tcr
> {standard input}:146: Error: unsupported relocation against tsr
> {standard input}:154: Error: unsupported relocation against tsr
> make[1]: *** [cpu_init.o] Error 1
>
> Shouldn't this work?
It *should*. But unfortunately it doesn't. I just checked this here myself. I
get the same error. Seems that the "tcr/tsr" defines need to be converted to
upper-case. It would be great if you could send a patch for this.
> Also I would like to determine in u-boot if a
> reset was caused by the watchdog timer using the TSR WRS field. If it
> was reset by the watchdog we will boot into a failsafe partition to
> protect against system update errors.
>
> Has anyone done something like this?
Such a detection is not implemented for PPC4xx. Not sure if it's implemented
for any other architecture.
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2010-05-20 11:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 22:27 [U-Boot] Watchdog support for ppc4xx Mark Maestas
2010-05-20 11:55 ` Stefan Roese [this message]
2010-05-20 17:58 ` Mark Maestas
2010-05-20 18:46 ` Wolfgang Denk
2010-05-21 9:05 ` Detlev Zundel
2010-06-04 18:26 ` Mark Maestas
2010-06-04 19:46 ` Wolfgang Denk
2010-06-04 20:14 ` Mark Maestas
2010-07-07 17:54 ` Chen Wen
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=201005201355.01964.sr@denx.de \
--to=sr@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.