From: "Frank Robbins" <Frank.Robbins@Analogue-Micro.com>
To: <acurtis@onz.com>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: problems with MPC8xx internal RTC !?
Date: Wed, 29 Jan 2003 15:20:44 -0000 [thread overview]
Message-ID: <004001c2c7aa$00637140$870ca8c0@hercules> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFCEICEBAA.acurtis@onz.com
There is no patch .. If we could patch the hardware we would all be happy!
The chip is ill there was a Mask error when it was originally made. It has
never been fixed on the 860T , and on most of the 855T silicon this was also
the case.. though it was down for a fix on of the errata sheets whether this
has been done I am unsure check www.mot-sps.com
The fix is to use a RTC clock chip and not use the VKAPWR just connect it to
3V3 (Don't leave it disconnected otherwise you will be able fry eggs on the
chip.. it gets hot when left unconnected). Change your hardware to use a RTC
chip or live with the power drain.
Frank
----- Original Message -----
From: "Allen Curtis" <acurtis@onz.com>
To: "Frank Robbins" <Frank.Robbins@Analogue-Micro.com>; "Steven Scholz"
<steven.scholz@imc-berlin.de>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, January 29, 2003 2:53 PM
Subject: RE: problems with MPC8xx internal RTC !?
> > Just an a side note has the errata for the RTC been fixed on the
> > MPC855T it
> > is not fixed on the 860T and I believe this feature is now missing on
> > future MPC 866T, 857 variants.
>
> Do you have a patch you would like to contribute?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-01-29 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 9:05 problems with MPC8xx internal RTC !? Steven Scholz
2003-01-29 10:55 ` Frank Robbins
2003-01-29 14:53 ` Allen Curtis
2003-01-29 15:20 ` Frank Robbins [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='004001c2c7aa$00637140$870ca8c0@hercules' \
--to=frank.robbins@analogue-micro.com \
--cc=acurtis@onz.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).