All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frank Robbins" <Frank.Robbins@Analogue-Micro.com>
To: "Steven Scholz" <steven.scholz@imc-berlin.de>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: problems with MPC8xx internal RTC !?
Date: Wed, 29 Jan 2003 10:55:15 -0000	[thread overview]
Message-ID: <003601c2c784$e92ebcc0$870ca8c0@hercules> (raw)
In-Reply-To: 3E37996A.40302@imc-berlin.de


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.

If not it will draw several mA from your battery and discharge it very
quickly

Frank

----- Original Message -----
From: "Steven Scholz" <steven.scholz@imc-berlin.de>
To: "Linuxppc-Embedded" <linuxppc-embedded@lists.linuxppc.org>
Sent: Wednesday, January 29, 2003 9:05 AM
Subject: problems with MPC8xx internal RTC !?


>
> Hi there,
>
> I am using an MPC855T, external clocked with 16 MHz. Using the internal
PLLs it
> runs at 80MHz/40Mhz. An 32.768KHZ crystal is connected to clock the MPCs
> internal RTC. A battery is there as well.
>
> All seems to be fine. But I realized that the RTC runs too fast. It seems
to be
> releated to systems restarts.
>
> It tested. After 25 reboots the RTC is already SIX seconds ahead!!!
>
> rdate:   Wed Jan 29 10:03:58 2003
> date:    Wed Jan 29 10:04:04 CET 2003
> hwclock: Wed Jan 29 10:04:04 2003  0.000000 seconds
>
> Any ideas?
>
> Thanks,
>
> Steven
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-01-29 10:55 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 [this message]
2003-01-29 14:53   ` Allen Curtis
2003-01-29 15:20     ` Frank Robbins

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='003601c2c784$e92ebcc0$870ca8c0@hercules' \
    --to=frank.robbins@analogue-micro.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=steven.scholz@imc-berlin.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.