From: pravin <pravin3560@yahoo.com>
To: linuxppc-embedded@ozlabs.org
Subject: U-boot1.1.4 porting problem on PPC 440GX
Date: Tue, 2 May 2006 15:32:59 -0700 (PDT) [thread overview]
Message-ID: <20060502223259.55214.qmail@web50512.mail.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 759 bytes --]
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.
Thanks,
Pravin
[-- Attachment #2: Type: text/html, Size: 919 bytes --]
next reply other threads:[~2006-05-02 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 22:32 pravin [this message]
2006-05-02 22:55 ` U-boot1.1.4 porting problem on PPC 440GX Eugene Surovegin
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=20060502223259.55214.qmail@web50512.mail.yahoo.com \
--to=pravin3560@yahoo.com \
--cc=linuxppc-embedded@ozlabs.org \
/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