public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Markus Klotzbücher" <mk@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot AMCC yosemite board 440EP
Date: Fri, 29 Sep 2006 12:03:20 +0200	[thread overview]
Message-ID: <87zmcjrnvb.fsf@denx.de> (raw)
In-Reply-To: <DA3CC5B292645843B5E8C544EFBC71B6310222@exchange1.jetter.local> (Tobias Föll's message of "Fri, 29 Sep 2006 10:44:22 +0200")

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

  reply	other threads:[~2006-09-29 10:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29  8:44 [U-Boot-Users] U-boot AMCC yosemite board 440EP Föll, Tobias
2006-09-29 10:03 ` Markus Klotzbücher [this message]
2006-10-04  6:36   ` Föll, Tobias
2006-10-05 15:38     ` Wolfgang Denk
2006-09-29 18:09 ` Stefan Roese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zmcjrnvb.fsf@denx.de \
    --to=mk@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox