public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-boot AMCC yosemite board 440EP
Date: Fri, 29 Sep 2006 20:09:15 +0200	[thread overview]
Message-ID: <200609292009.16044.sr@denx.de> (raw)
In-Reply-To: <DA3CC5B292645843B5E8C544EFBC71B6310222@exchange1.jetter.local>

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

      parent reply	other threads:[~2006-09-29 18:09 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
2006-10-04  6:36   ` Föll, Tobias
2006-10-05 15:38     ` Wolfgang Denk
2006-09-29 18:09 ` Stefan Roese [this message]

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=200609292009.16044.sr@denx.de \
    --to=sr@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