[U-Boot-Users] U-boot AMCC yosemite board 440EP

[U-Boot-Users] U-boot AMCC yosemite board 440EP

[Föll, Tobias]

Hi,

i have a hardware which is very near to the yosemite board called JC-670.
The yosemite board has 4 DDR chips and my hardware has only two chips (2*Micron 64V16M16 has 256Mbit...),
because i need only 256MBit*2Chips=512MBit=64Mbyte.

It seem that i have problems with the DDR interface. 
I downloaded the u-boot bin file from the AMCC -> denx page, and programmed it into
the flash on my hardware called JC-670.
On the serial output i saw that the system starts up. But then it hangs...

Here is the first output hardware JC-670:
===========================================
U-Boot 1.1.4-ga2c95a72 (Jul 28 2006 - 19:32:28)

CPU:   AMCC PowerPC 440EP Rev. B at 666.666 MHz (PLB=266, OPB=133, EBC=133 MHz)
       I2C boot EEPROM enabled
       Internal PCI arbiter disabled, PCI async ext clock used
       32 kB I-Cache 32 kB D-Cache
Board: Yosemite - AMCC PPC440EP Evaluation Board
I2C:   ready
DRAM:

Software has not detected the DRAM !

Here is the second output hardware JC-670:
==========================================

U-Boot 1.1.4-ga2c95a72 (Jul 28 2006 - 19:32:28)

CPU:   AMCC PowerPC 440EP Rev. B at 666.666 MHz (PLB=266, OPB=133, EBC=133 MHz)
       I2C boot EEPROM enabled
       Internal PCI arbiter disabled, PCI async ext clock used
       32 kB I-Cache 32 kB D-Cache
Board: Yosemite - AMCC PPC440EP Evaluation Board
I2C:   ready
DRAM:  256 MB

U-boot software has detected the DRAM's.



I can try this several times the difference is that sometimes i got the DRAM size(like first output) and somtimes not (like second output).
Thats all. Must i change the u-boot code if i only use two DDR Chips ?

On the moment i can not generate a new u-boot bin , because it will not work with cygwin under windows.I tried it. 
And i'am not a linux expert, because of this i can not do this work under linux on the moment.

Has anybody an idea why sometimes the "256 MB" text will not come ?

For me it looks like the sdram_init() function in yosemite.c sometimes hangs.

Regards

Tobias 

[U-Boot-Users] U-boot AMCC yosemite board 440EP

[Markus Klotzbücher]

Hi Tobias,

"F?ll, Tobias" <TFoell@jetter.de> writes:

> i have a hardware which is very near to the yosemite board called
> JC-670.
> The yosemite board has 4 DDR chips and my hardware has only two chips
> (2*Micron 64V16M16 has 256Mbit...),
> because i need only 256MBit*2Chips=512MBit=64Mbyte.

Are the chips on both boards identical?

> It seem that i have problems with the DDR interface. 
> I downloaded the u-boot bin file from the AMCC -> denx page, and
> programmed it into
> the flash on my hardware called JC-670.
> On the serial output i saw that the system starts up. But then it
> hangs...

It seems to me that the SDRAM initialization for your new board is
broken/incomplete. You need to fix it.

> I can try this several times the difference is that sometimes i got
> the DRAM size(like first output) and somtimes not (like second
> output).
> Thats all. Must i change the u-boot code if i only use two DDR Chips ?

Not necessarily, but in your case it seems so.

> On the moment i can not generate a new u-boot bin , because it will
> not work with cygwin under windows.I tried it.
> And i'am not a linux expert, because of this i can not do this work
> under linux on the moment.

Well, maybe this is the right time to become one?

Regards

Markus Klotzbuecher

[U-Boot-Users] U-boot AMCC yosemite board 440EP

[Stefan Roese]

Hi Tobias,

On Friday 29 September 2006 10:44, F?ll, Tobias wrote:
> i have a hardware which is very near to the yosemite board called JC-670.
> The yosemite board has 4 DDR chips and my hardware has only two chips
> (2*Micron 64V16M16 has 256Mbit...), because i need only
> 256MBit*2Chips=512MBit=64Mbyte.

It's not only a matter of the amount of chips, but also of the density, the 
speed, etc...

The yoesmite has a fixed initialization for it's DDR setup. It will only work 
on a board with the same DDR setup, which you _don't_ have!

<snip>

> I can try this several times the difference is that sometimes i got the
> DRAM size(like first output) and somtimes not (like second output). Thats
> all. Must i change the u-boot code if i only use two DDR Chips ?

Yes!!!

> On the moment i can not generate a new u-boot bin , because it will not
> work with cygwin under windows.I tried it. And i'am not a linux expert,
> because of this i can not do this work under linux on the moment.

Sorry, but without changing the code and rebuilding an image you have no 
chance. Of course you also could hire an expert (hint!) to do this. ;-)

Best regards,
Stefan

[U-Boot-Users] U-boot AMCC yosemite board 440EP

[Föll, Tobias]

 

-----Urspr?ngliche Nachricht-----
Von: Markus Klotzb?cher [mailto:mk at denx.de] 
Gesendet: Freitag, 29. September 2006 12:03
An: F?ll, Tobias
Cc: u-boot-users at lists.sourceforge.net
Betreff: Re: [U-Boot-Users] U-boot AMCC yosemite board 440EP

Hi Tobias,

"F?ll, Tobias" <TFoell@jetter.de> writes:

> i have a hardware which is very near to the yosemite board called 
> JC-670.
> The yosemite board has 4 DDR chips and my hardware has only two chips 
> (2*Micron 64V16M16 has 256Mbit...), because i need only 
> 256MBit*2Chips=512MBit=64Mbyte.

Are the chips on both boards identical?


Tobias: Yes !

> It seem that i have problems with the DDR interface. 
> I downloaded the u-boot bin file from the AMCC -> denx page, and 
> programmed it into the flash on my hardware called JC-670.
> On the serial output i saw that the system starts up. But then it 
> hangs...

It seems to me that the SDRAM initialization for your new board is broken/incomplete. You need to fix it.

Tobias: But i programmed the original u-boot into the flash. Because of this it is the correct 
Initialization !

> I can try this several times the difference is that sometimes i got 
> the DRAM size(like first output) and somtimes not (like second 
> output).
> Thats all. Must i change the u-boot code if i only use two DDR Chips ?

Not necessarily, but in your case it seems so.

> On the moment i can not generate a new u-boot bin , because it will 
> not work with cygwin under windows.I tried it.
> And i'am not a linux expert, because of this i can not do this work 
> under linux on the moment.

Well, maybe this is the right time to become one?

Regards

Markus Klotzbuecher

[U-Boot-Users] U-boot AMCC yosemite board 440EP

[Wolfgang Denk]

Dear Tobias,

please start reading http://www.afaik.de/usenet/faq/zitieren/

In message <DA3CC5B292645843B5E8C544EFBC71B6310296@exchange1.jetter.local> you wrote:
> 
> It seems to me that the SDRAM initialization for your new board is broken/
> incomplete. You need to fix it.
> 
> Tobias: But i programmed the original u-boot into the flash. Because of this
> it is the correct Initialization !

It is the correct initialization for the yosemite board, but not for
your hardware. You must *port* U-Boot to your hardware.

This has been explained to you before.

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
When some people discover the truth, they just can't  understand  why
everybody isn't eager to hear it.