On Thu, Oct 23, 2008 at 10:39:11AM +0200, Stefan Roese wrote:
>
> Ayman, which module are you using and what's your reg 21 value? Does anybody
> have the time to dig into those specs to find a common solution?
>
I am using a Kingston mini-dimm, my reg 21 value is 0x4, so 1 pll / 1 reg.
For reg
On Thursday 23 October 2008, Felix Radensky wrote:
> >> I've changed
> >>
> >> if ((attribute & 0x02) == 0x00)
> >>
> >> to be
> >>
> >> if (((attribute & 0x02) == 0x00) && (attribute != 0x04))
> >
> > Why did you change it this way? Which DDR2 module are you using? And
> > what's the value of SPD
Hi, Stefan
Stefan Roese wrote:
> Felix,
>
> On Thursday 23 October 2008, Felix Radensky wrote:
>
>> I had the same problem with u-boot-1.3.4 on custom 460EX board with
>> registered SODIMM. The SPD code in 4xx_spd_ddr2.c (program_copt1())
>> checks two SPD fields to decide whether DIMM is regi
Felix,
On Thursday 23 October 2008, Felix Radensky wrote:
> I had the same problem with u-boot-1.3.4 on custom 460EX board with
> registered SODIMM. The SPD code in 4xx_spd_ddr2.c (program_copt1())
> checks two SPD fields to decide whether DIMM is registered: DDRII DIMM
> type (offset 20) and SDR
Hi,
I had the same problem with u-boot-1.3.4 on custom 460EX board with
registered SODIMM. The SPD code in 4xx_spd_ddr2.c (program_copt1())
checks two SPD fields to decide whether DIMM is registered: DDRII DIMM
type (offset 20) and SDRAM module attributes (offset 21).
In my case, the values in t
On Thursday 23 October 2008, Ayman M. El-Khashab wrote:
> On Wed, Oct 22, 2008 at 07:12:30AM +0200, Stefan Roese wrote:
> > Yes, there have been issues with the "old" autocalibration code on some
> > boards. That's one reason that AMCC provided a new version just a few
> > weeks ago:
>
> Thanks Ste
On Wed, Oct 22, 2008 at 07:12:30AM +0200, Stefan Roese wrote:
>
> Yes, there have been issues with the "old" autocalibration code on some
> boards. That's one
> reason that AMCC provided a new version just a few weeks ago:
>
Thanks Stefan, I've got the hardware mostly working now. The new c
On Tuesday 21 October 2008, Ayman M. El-Khashab wrote:
> > How about reading the code?
>
> (Looking at canyonlands.h)
>
> Ok, I took a look at this and the autocalibration is not obvious. It looks
> like there is a currently a hardcoded RQDC value of 8038. If this is
> undefined then the code
On Tue, Oct 21, 2008 at 09:10:03PM +0200, Wolfgang Denk wrote:
> >
> > I should have mentioned that we have DEBUG enabled and we've also
> > run the RAM test that is included in u-boot. The ram test does pass.
>
> Please see the FAQ, entry # 1. Passing the RAM test does not mean
> anything whe
Dear "Ayman M. El-Khashab",
In message <[EMAIL PROTECTED]> you wrote:
>
> I should have mentioned that we have DEBUG enabled and we've also
> run the RAM test that is included in u-boot. The ram test does pass.
Please see the FAQ, entry # 1. Passing the RAM test does not mean
anything when it
Thank you Stefan,
On Tue, Oct 21, 2008 at 05:54:21PM +0200, Stefan Roese wrote:
> On Tuesday 21 October 2008, Ayman M. El-Khashab wrote:
> > it is stuck inside the relocation or immediately after it branches
> > to the code in RAM.
>
> I suggest that you enable DEBUG in lib_ppc/board.c (define DE
On Tuesday 21 October 2008, Ayman M. El-Khashab wrote:
> We've got our custom hardware in and are having trouble getting
> u-boot to start up. We've modeled our board close to the canyonlands.
> The main differences are no sensors, DIMM at 0x51, and a 16Mb NOR
> flash instead of 64Mb. We boot and
Hello,
We've got our custom hardware in and are having trouble getting
u-boot to start up. We've modeled our board close to the canyonlands.
The main differences are no sensors, DIMM at 0x51, and a 16Mb NOR
flash instead of 64Mb. We boot and get messages and we've determined
it is stuck inside t
13 matches
Mail list logo
