linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jerry Van Baren <vanbaren_gerald@si.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: 66 Mhz bus clock for EST8260?
Date: Fri, 08 Dec 2000 15:09:42 -0500	[thread overview]
Message-ID: <4.3.2.20001208145914.00ba75b0@falcon.si.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0012081225350.24199-100000@eos>


Yes, that is what we did and it worked, including running linux, as I
recall.

We have not run extensively with the 66MHz bus clock.  Our processor
was 166/133/66 rev A.1 so we clocked the processor at 166MHz (MODCK_H =
0101, MODCK[1-3] = 110).  We played with overclocking the CPU: we were
able to run quite a bit faster than 166MHz at the 33MHz bus speed
(300MHz?), but died right away when we tried to overclock with the
66MHz bus speed.

For more details, I would have to dig out some notes.

gvb


At 12:47 PM 12/8/00 -0600, Brian Ford wrote:

>Is there any magic in getting the EST8260 board to work with a 66 Mhz bus
>clock?  I haven't had good luck with a Linux or vxWorks image.
>
>My board has a 200/166/66 rev A.1 chip.
>
>I boot using a vxWorks bootrom.  I have made a few corrections to the
>bootrom so the decrementer frequency is set correctly from the user
>dip switches in addition to setting the core, cpm, and bus speeds.
>
>The scenerio is as follows:
>
>1.) Burn configuration word to change MODCK_H from 0x0001 to 0x0101
>2.) Swap oscillators 33.0 -> 66.0 Mhz
>3.) Set MODCK[1-3] switches to 0x111 (200/133/66)
>4.) Mirror 3.) on user switches for vxWorks bootrom to read
>5.) Hack head_8260.S to put immr in place for Linux
>6.) Set linux board info in embed_config.c to 200/133/66/66
>(core,cpm,bus,brg) making sure there is real space allocated for it
>instead or whatever was in r3 when vxWorks booted us.
>6.) Reboot.
>
>vxWorks bootrom runs fine and downloads Linux or vxWorks.
>
>Linux pannics just before giving me a shell prompt somewhere in tty init.
>
>vxWorks appears to come up fine, but the muxDevBind fails for the Fast
>Ethernet and thus no network communications.  Even though the bootrom
>just downloaded us successfully over the same interface.
>
>Has anyone had any luck with the 66 Mhz bus clock?
>
>--
>Brian Ford
>Software Engineer
>Vital Visual Simulation Systems
>FlightSafety International
>Phone: 314-551-8460
>Fax:   314-551-8444
>
>


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

  parent reply	other threads:[~2000-12-08 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-08 18:47 66 Mhz bus clock for EST8260? Brian Ford
2000-12-08 19:03 ` Dan Malek
2000-12-08 21:55   ` Jerry Van Baren
2000-12-08 20:09 ` Jerry Van Baren [this message]
     [not found] <7283DE19D141D111AD0E00A0C95B195502581E41@mail2.aiinet.com>
2000-12-11 15:32 ` Brian Ford
2000-12-11 16:47   ` Stephen B. Johnson

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=4.3.2.20001208145914.00ba75b0@falcon.si.com \
    --to=vanbaren_gerald@si.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).