[U-Boot] Trouble moving custom MPC8548 board to U-boot 1.3

[Ajeesh Kumar]

Hi Pieter,

>I have managed to read the SPD data for the dram. I also confirmed that the
dram control and timing settings correspond to the settings that worked in
the >
>previous uboot.
So it mean that you r using a DIMM, where the configurations are available
on the EEPROM.
Make sure u've decoded those values and put in below registers 
CS0_BNDS
CS1_BNDS
CS2_BNDS
CS3_BNDS
CS0_CONFIG
CS1_CONFIG
CS2_CONFIG
CS3_CONFIG
TIMING_CFG_3(EXT_REFREC)
TIMING_CFG_0
TIMING_CFG_1
TIMING_CFG_2
DDR_CFG
DDR_CFG_2
DDR_MODE
DDR_MODE_2
DDR_INTERVAL
DDR_CLK_CNTL
;DELAY   200
DDR_CFG

>I am now able to run uboot up to the "relocate_code". The new Stack pointer
is set to 0x0FF8DF58 witch is close enough to what i expected.
>This is however where the board hangs. (The board also hang when running
the "testram").  I tried reading the data at the new stack pointer but get
"SAP: read >
>access failed"  i get the same error when trying to read any address within
the RAM or any address of other devices.  This leads me to think that my LAW
or >
>TLB setup is incorrect.

After initializing the ram, the next thing u-boot does is relocating the
monitor code from the Flast to the ram. If this fails then it might be some
problem in accessing ram. This happens when the LAW is not properly
initialized and the memory is not mapped properly. Make sure you map ur DDR.

Thanks,
Ajeesh Kumar

-----Original Message-----
From: u-boot-bounces at lists.denx.de [mailto:u-boot-bounces at lists.denx.de] On
Behalf Of Pieter
Sent: Monday, January 12, 2009 1:45 PM
To: u-boot at lists.denx.de
Subject: [U-Boot] Trouble moving custom MPC8548 board to U-boot 1.3

Hi all,
>> I have spent quite some time trying to move from U-Boot 1.2 to a 
>> newer version.. I am stuck at the initialization of the ram. The ram 
>> checksum fails and gives me a "total memory of 0". (the board has 
>> 512MB and work when booting uboot 1.2)
>>
>> can anyone pls. point me in the right direction?
>>
>>
> This is your root cause:  Unable to get the SPD information for the 
> DDR DIMM in slot 0 of controller 0.
>
> What part are you using?  Does it support SPD?
> Is your I2C to it hooked up correctly?
> Can you dump the SPD information that is read?
> Does it match the part specs?
>
> HTH,
> jdl
I have managed to read the SPD data for the dram. I also confirmed that the
dram control and timing settings correspond to the settings that worked in
the previous uboot.
I am now able to run uboot up to the "relocate_code". The new Stack pointer
is set to 0x0FF8DF58 witch is close enough to what i expected.
This is however where the board hangs. (The board also hang when running the
"testram").  I tried reading the data at the new stack pointer but get "SAP:
read access failed"  i get the same error when trying to read any address
within the RAM or any address of other devices.  This leads me to think that
my LAW or TLB setup is incorrect.

Looking at LAW setup: (based on board sbc8548)

   /* LAW(Local Access Window) configuration:
    * 0x0000_0000     0x1fff_ffff     DDR             512M/Auto
    * 0x8000_0000     0xbfff_ffff     PCI1 MEM        1G
    * 0xc000_0000     0xcfff_ffff     PCI1 IO         16M
    * 0xe000_0000     0xffff_ffff      LBC                       512M */

   struct law_entry law_table[] = {
   #ifndef CONFIG_SPD_EEPROM
           SET_LAW(CONFIG_SYS_DDR_SDRAM_BASE, LAWAR_SIZE_512M,
   LAWAR_TRGT_IF_DDR),
   #endif
           SET_LAW(CONFIG_SYS_PCI1_MEM_PHYS, LAWAR_SIZE_1G,
   LAWAR_TRGT_IF_PCI1 ),
           SET_LAW(CONFIG_SYS_PCI1_IO_PHYS, LAWAR_SIZE_16M,
   LAWAR_TRGT_IF_PCI1),
           SET_LAW(CONFIG_SYS_LBC_BASE, LAWAR_SIZE_512M, LAWAR_TRGT_IF_LBC)
   };

Since my board uses SPD_EEPROM, where does the LAW entry for DDR get
initilized or should the #ifndef statement be removed?


Am I on the  right track to solving my problem?
thanks pieter
_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments contained in it.