LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Eugene Surovegin <ebs@ebshome.net>
To: pravin <pravin3560@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: U-boot1.1.4 porting problem on PPC 440GX
Date: Tue, 2 May 2006 15:55:40 -0700	[thread overview]
Message-ID: <20060502225540.GA25045@gate.ebshome.net> (raw)
In-Reply-To: <20060502223259.55214.qmail@web50512.mail.yahoo.com>

On Tue, May 02, 2006 at 03:32:59PM -0700, pravin wrote:
> Hi All,
>   I build uboot1.1.4 for ocotea_config  and run on an ocotea without SPD on DIMMS (SDRAM) and  It works. We manufactured another board derived from Ocotea Ref design, 440GX processor and on baord SDRAM (DIMMS) 256MB discrete parts. I use the same Uboot1.1.4 for this board. It boots upto calling the 
>    
>   relocate_code in cpu/ppc4xx/start.S and hangs. The same code works well on Ocotea. I run the memory tests and it passed all.
>    
>   Any idea why this could hang and never finish the relocate_code function. Trying relocating Uboot to SDRAM memory to get the C environment and run from memory.
>    
>   Any help would be appreciated. Any idea if i need any special code because of the discrete parts of SDRAM on our board.

You can use Ocotea code (kernel and/or U-Boot) as-is for your board 
only in one case - your board is _identical_ to Ocotea.

I doubt that this is the case, so you have to modify U-Boot and/or 
kernel board support code to accommodate any differences between Ocotea 
and your design.

Start with asking your hardware people about such differences.

-- 
Eugene

  reply	other threads:[~2006-05-02 22:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 22:32 U-boot1.1.4 porting problem on PPC 440GX pravin
2006-05-02 22:55 ` Eugene Surovegin [this message]
2006-05-02 23:34   ` Wolfgang Denk

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=20060502225540.GA25045@gate.ebshome.net \
    --to=ebs@ebshome.net \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=pravin3560@yahoo.com \
    /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