[U-Boot-Users] Problem about porting u-boot 1.1.4 to MPC8560

[U-Boot-Users] Problem about porting u-boot 1.1.4 to MPC8560

[enorm]

Hi,
    After prog u-boot image to 8560. We get output as follows:



U-Boot 1.1.4 (Sep  4 2006 - 17:15:31)

CPU:   8560, Version: 1.0, (0x80700010)
Core:  E500, Version:
Clock Configuration:- 19:56:59)
       CPU: 825 MHz, CCB: 330 MHz,, Version: 1.0, (0x80700010)
       DDR: 165 MHz, LBC:  82 MHzCore:  E500, Version: 1.0, (0x802
L1:    D-cache 32 kB enabled
Clock Confi
       I-cache 32 kB enabled
       CPU: 792 MHz, CCB: 2
Board: ADS
    PCI1: 32 bit, 33 MHz (compiled) MHz, LBC:  66 MHz
I2C:   ready
L1:    D
DRAM:  Initializing
 32 kB enabled
DDR: number of ranks = 1: ADS
    PCI1
DDR: DDR I rank density = 0x10000000
I2C:   rea

DDR: cs0_bnds   = 0x0000000fzing
DDR:
DDR: cs0_config = 0x80000102
DDR: DDR I r
DDR: caslat SPD bit is 4
DDR: tCKmin = 5000 psbnds   = 0x00000007
DDR: sdram_mode_2 = 0x00000000
DDR: sdram_interval = 0x05080100
DDR: sdram_cfg_2  = 0x00000000
DDR: sdram_cfg   = 0xc2000000
DDR: MAS0=0x10080000
DDR: MAS1=0xc0000900
DDR: MAS2=0x00000000
DDR: MAS3=0x00000015
DDR: LAWBAR1=0x00000000
DDR: LARAR1=0x80f0001b
    SDRAM: 64 MB
    DDR: 256 MB
Top of RAM usable for U-Boot at: 10000000
Reserving 173k for U-Boot at: 0ffd0000
Reserving 136k for malloc() at: 0ffae000
Reserving 88 Bytes for Board Info at: 0ffadfa8
Reserving 72 Bytes for Global Data at: 0ffadf60
Stack Pointer at: 0ffadf48



then it can't go on running. we checked ,found it falled in "relocate_code"
,then we write a progam to test memory, we found test failed(say write some
thing to 0-0x8000000 then read)



How can we do to fix this problem?

[U-Boot-Users] Problem about porting u-boot 1.1.4 to MPC8560

[Wolfgang Denk]

In message <008101c6d012$e6948680$a309a8c0@cdf28e684a26482> you wrote:
>
> then it can't go on running. we checked ,found it falled in "relocate_code"
> ,then we write a progam to test memory, we found test failed(say write some
> thing to 0-0x8000000 then read)

So you obviously have either some hardware problem with your RAM,
and/or bugs in your RAM init code.

> How can we do to fix this problem?

Review the hardware and your chnages to the code.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Parkinson's Law:  Work expands to fill the time alloted it.

[U-Boot-Users] Problem about porting u-boot 1.1.4 to MPC8560

[Steve Williams]

enorm wrote:
> 
> Hi,
>     After prog u-boot image to 8560. We get output as follows:

With my recent port for the 8560 for our custom board we found that the
8560 does not work properly with some makes of DDR modules. Have you
tried some different RAM with your board?

Tell us a bit more about your RAM

> 
> 
> 
> then it can't go on running. we checked ,found it falled in "relocate_code"
> ,then we write a progam to test memory, we found test failed(say write some
> thing to 0-0x8000000 then read)
>

Looks like the RAM is not set-up correctly at all - you will need to go
through the settings using the RAM data sheet and the 8560RM book. Make
sure the settings being derived by "spd_eeprom" are what you expect.

Also when you get it working with your RAM test you may still get
problems with your OS. We ended up having to hand pick RAM for this
processor with our board. I would be interested in seeing how you get on.

We have moved on to the the 8548 for our B-Model and I have had to make
changes to "spd_eeprom.c" to accommodate our RAM. I am hoping to provide
this back as a patch when I am sure it works OK with our OS (QNX).


Steve Williams

[U-Boot-Users] Problem about porting u-boot 1.1.4 to MPC8560

[enorm]

>So you obviously have either some hardware problem with your RAM,
and/or bugs in your RAM init code.

we can see from the out put, u-boot can recognize the frequence  of  the 
momery, and more info. through spd.

>> How can we do to fix this problem?

>>Review the hardware and your chnages to the code.



we use MT9VDDT1672AG first,  then, KVR400X64C3A, both can't work.





----- Original Message ----- 
From: "Wolfgang Denk" <wd@denx.de>
To: "enorm" <enorm@126.com>
Cc: <u-boot-users@lists.sourceforge.net>
Sent: Monday, September 04, 2006 8:31 PM
Subject: Re: [U-Boot-Users] Problem about porting u-boot 1.1.4 to MPC8560


In message <008101c6d012$e6948680$a309a8c0@cdf28e684a26482> you wrote:
>
> then it can't go on running. we checked ,found it falled in 
> "relocate_code"
> ,then we write a progam to test memory, we found test failed(say write 
> some
> thing to 0-0x8000000 then read)

So you obviously have either some hardware problem with your RAM,
and/or bugs in your RAM init code.

> How can we do to fix this problem?

Review the hardware and your chnages to the code.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Parkinson's Law:  Work expands to fill the time alloted it.

[U-Boot-Users] Problem about porting u-boot 1.1.4 to MPC8560

[Wolfgang Denk]

In message <013901c6d023$2cacc230$a309a8c0@cdf28e684a26482> you wrote:
> 
> we can see from the out put, u-boot can recognize the frequence  of  the 
> momery, and more info. through spd.

Did you verify that the information is correct for your hardware? Did
you verify that the remaining parts of the init sequence are  ok  for
your hardware? Did you verify that your hardware is OK?

> >>Review the hardware and your chnages to the code.
> 
> we use MT9VDDT1672AG first,  then, KVR400X64C3A, both can't work.

Yes, that's what I meant when I wrote "review the hardware and your
changes to the code."

And please stop top posting/full quoting; please see
http://www.netmeister.org/news/learn2quote.html

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
The IQ of the group is the lowest IQ of a member of the group divided
by the number of people in the group.