Skip to contentSkip to conversation

MPC8360E & Large DDR Capacities

U-Boot-Users Russell McGuire 2 participants 3 messages Dec 18, 2006 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): mailman.113204.1166449236.30209.u-boot-users@lists.sourceforge.net

#1 lore raw

All

After digging around it would seem that U-boot is resetting after the first direct access to DDR memory. I placed a number of statements and installed a 'memory test' function.

I think the DDR init is failing due to the udelay(200) function early in the MPC8360E-MDS board files. The delay does not seem to be operational, so I 'think' the DDR gets enabled before the specked 200us delay that the MPC8360 manual requires.

Anyone have any ideas what might cause the udelay function to not 'delay' as advertised. <My core clock is setup@533 Mhz, but 200us should be will within the non-overflow capability>.

-Russ
-----Original Message-----
From: Timur Tabi [mailto:timur at freescale.com]
Sent: Monday, December 18, 2006 7:53 AM
To: rmcguire at videopresence.com
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] MPC8360E & Large DDR Capacities

Quoted 2 lines · Russell McGuire

Does anybody know if there are any issues with using DDR capacities above 256MB? I am attempting to use a 512MB DIMM at the moment, and am not sure

if

Quoted 2 lines

I am getting a SDRAM init issue that is causing U-boot to continuously reset,

It would be very helpful if you could narrow down the exact line of code that is
causing the reset.

Signature · 2 lines
Timur Tabi
Linux Kernel Developer @ Freescale
#2 lore raw
Quoted 4 lines · Russell McGuire

I think the DDR init is failing due to the udelay(200) function early in the MPC8360E-MDS board files. The delay does not seem to be operational, so I 'think' the DDR gets enabled before the specked 200us delay that the MPC8360 manual requires.

Have you tried creating your own delay function that waits several seconds, just to be sure? A for-loop would do.

Signature · 2 lines
Timur Tabi
Linux Kernel Developer @ Freescale
#3 lore raw

All,

I found the first error.

The MPC8360EMDS.c file is missing a single write during the startup sequence. This is also an error in the MPC8360E family manual I found about 2 weeks ago, though I notified Freescale, nobody has issued a revised manual yet.

The DDR_SDRAM_CLK_CNTL register is missing two bit fields in the manual, though it's the same as the MPC8349E so one can read the 8349E manual to get the right info, see 9.4.1.14 in the MPC8360E for the bad info.

Anyway added the following line to the MPC8360EMDS board and now DDR will initialize.

ADD:

im->ddr.sdram_clk_cntl = 0x83000000;

Note the '8' is the undocumented bit. SS_EN I think is the name.

Anyway, now I can get up to the 'relocate_code' call. So we'll see if the DDR is stable enough for full speed execution.

Russell McGuire
Systems Engineer
VideoPresence, Inc.
rmcguire at videopresence.com
503.888.0968

-----Original Message-----
From: Timur Tabi [mailto:timur at freescale.com]
Sent: Monday, December 18, 2006 3:32 PM
To: rmcguire at videopresence.com
Cc: u-boot-users at lists.sourceforge.net
Subject: Re: [U-Boot-Users] MPC8360E & Large DDR Capacities

Quoted 1 line · Russell McGuire

I think the DDR init is failing due to the udelay(200) function early in

the

Quoted 2 lines

MPC8360E-MDS board files. The delay does not seem to be operational, so I 'think' the DDR gets enabled before the specked 200us delay that the

MPC8360

Quoted 1 line

manual requires.

Have you tried creating your own delay function that waits several seconds, just
to be sure? A for-loop would do.

Signature · 2 lines
Timur Tabi
Linux Kernel Developer @ Freescale