<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Stefan Roese 提到, 於 2008/6/30 下午 02:03:
<blockquote cite="mid:200806300803.40847.sr@denx.de" type="cite">
<pre wrap="">On Monday 30 June 2008, Yi-Neng Lin (林義能) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
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.
</pre>
</blockquote>
Thanks a lot for your reply, Stefan. However, in my understanding, only
memory-related info is stored in the EEPROM in the memory module, isn't
it? The CPU and bus related info is hard-coded in the code. This is
what I saw from my code. Not very sure of it, though.<br>
<blockquote cite="mid:200806300803.40847.sr@denx.de" type="cite">
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
Sure. You need to configure the PLL parameters accordingly. The 405EP users
manual should give you all the infos you need.
</pre>
</blockquote>
Yeah, I guess I've found them (or at least some of them.. :) )<br>
<blockquote cite="mid:200806300803.40847.sr@denx.de" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap="">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.
</pre>
</blockquote>
<pre wrap=""><!---->
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 */
</pre>
</blockquote>
I think it's the spd_sdram() [cpu/ppc4xx] who does the job, which
could have been an outdated method. The timing info is read from the
SPD (Serial Presence Detect) EEPROM on the SDRAM module. My question
is, with the upgraded CPU clock (333MHz), ordinary SDRAMs (PC100 and
PC133) may not be able to support it, which means I may have to use
PC2700 (333MHz; too fast?) or PC66(66MHz; too slow?). Am I correct? Any
other comment or solution for this?<br>
<br>
Yi-Neng<br>
<br>
<br>
<br>
</body>
</html>