public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CPU (405ep) clock upgrade..
Date: Mon, 30 Jun 2008 08:03:40 +0200	[thread overview]
Message-ID: <200806300803.40847.sr@denx.de> (raw)
In-Reply-To: <48687037.3000106@fiberlogic.com>

On Monday 30 June 2008, Yi-Neng Lin (???) wrote:
> We've got a board powered by 405ep running at 266MHz. Now we want to
> upgrade the clock rate to 333MHz (model: 3LB333C), can anyone give us
> some pointers doing this? I've tried to search the mailing list but
> found nothing quite related. Also there seems to exist very limited
> ports, if not none, of this model to which I may reference.

There are quite a big number of 405EP board ports. I suspect that some of them 
are capable of running with 333MHz. The frequencies are usually configured 
via the I2C bootstrap EEPROM.

> Below are questions that are more specific:
> 1. For CPU clock rate configuration, exactly what parameters should I
> modify? The suspected ones are FWDV (Feedback Divide) and FBDVB (Forward
> Divide B) which according to the processor user manual determines the
> PLLOUT A.

Sure. You need to configure the PLL parameters accordingly. The 405EP users 
manual should give you all the infos you need.

> 2. SDRAM clocking. I guess the clocking should be adapted to something
> like 111MHz (given the 333MHz CPU clock); however, the manual shows
> there there seems to be only two options, namely 100MHz and 133MHz.

Which SDRAM init code are you using? I suggest that you take a look at 
cpu/ppc4xx/sdram.c and use this file on your system too. You "only" need to 
configure some SDRAM chip parameters (for example include/configs/zeus.h):

/*
 * SDRAM configuration (please see cpu/ppc/sdram.[ch])
 */
#define CONFIG_SDRAM_BANK0      1       /* init onboard SDRAM bank 0 */
#define CONFIG_SDRAM_BANK1      1       /* init onboard SDRAM bank 1 */

/* SDRAM timings used in datasheet */
#define CFG_SDRAM_CL            3       /* CAS latency */
#define CFG_SDRAM_tRP           20      /* PRECHARGE command period */
#define CFG_SDRAM_tRC           66      /* ACTIVE-to-ACTIVE command period */
#define CFG_SDRAM_tRCD          20      /* ACTIVE-to-READ delay */
#define CFG_SDRAM_tRFC          66      /* Auto refresh period */

> 3. Clocking of others such as PCI (on-chip PLB clock, sync/async PCI
> clock) and serial port. Are they supposed to be modified accordingly?
> 4. Any other parameters?

You need to make sure that all frequencies are in range.

Best regards,
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
=====================================================================

  reply	other threads:[~2008-06-30  6:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30  5:33 [U-Boot-Users] CPU (405ep) clock upgrade "Yi-Neng Lin (林義能)"
2008-06-30  6:03 ` Stefan Roese [this message]
2008-06-30 12:01   ` "Yi-Neng Lin (林義能)"
2008-06-30 12:27     ` Stefan Roese
2008-07-02  9:23       ` Yi-Neng Lin
2008-07-02  9:38         ` Stefan Roese

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=200806300803.40847.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox