From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] MPC8280 Clock configuration for U-boot
Date: Thu, 06 Aug 2009 14:57:09 -0500 [thread overview]
Message-ID: <4A7B3595.7010101@freescale.com> (raw)
In-Reply-To: <20090806185644.1388.qmail@f4mail-234-237.rediffmail.com>
GurumurthyGowdar wrote:
> MPC8260 Clock Configuration
> - Bus-to-Core Mult 3x, VCO Div 4, 60x Bus Freq 16-50 , Core Freq 50-150
> - dfbrg 1, corecnf 0x10, busdf 4, cpmdf 1, plldf 0, pllmf 4, pcidf 3
> - vco_out 500000000, scc_clk 125000000, brg_clk 31250000
> - cpu_clk 300000000, cpm_clk 250000000, bus_clk 100000000
>
> CPU: MPC8260 (HiP7 Rev 14, Mask 1.0 1K49M) at 300 MHz
> Board: MPC8280 Based Remote IO CARD.SLN Technologies Pvt Ltd.
> I2C: ready
> DRAM: 512 MB
> FLASH: 256.5 MB
> *** Warning - bad CRC, using default environment
>
> In: serial
> Out: serial
> Err: serial
> Net: FCC2 ETHERNET
> RIO->
>
> in terms of hardware i have configured as per the clock configuration but if we see the
> above message i have a doubt regarding the 60x Bus Freq 16-50 --> but i have set 100
> MHZ, Core Freq 50-150 , i have set for 300 MHZ by checking the MPC8280EC i have
> configured the clock settings.
It looks like the strings such as 16-50, 50-150, etc. are redundant (the
computed value using clkin is also shown), unhelpful (it's not obvious
that it's supposed to be a range -- and what is the range really
supposed to tell you?), and just wrong (it assumes certain possible clkins).
Look at cpu_clk and bus_clk instead, which have the values you're expecting.
> if anyone ported U-boot 1.3.1 on MPC8280 send me the u-boot messages when booted or
> power on.
Why use such old code?
-Scott
next prev parent reply other threads:[~2009-08-06 19:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 18:56 [U-Boot] MPC8280 Clock configuration for U-boot GurumurthyGowdar
2009-08-06 19:49 ` Wolfgang Denk
2009-08-06 19:57 ` Scott Wood [this message]
2009-08-06 20:25 ` Jerry Van Baren
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=4A7B3595.7010101@freescale.com \
--to=scottwood@freescale.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