From: 郭劲 <guojin02@tsinghua•org.cn>
To: linuxppc-embedded@ozlabs•org
Subject: The question about the relocate_code on u-boot for MPC8360?
Date: Fri, 31 Aug 2007 10:13:27 +0800 [thread overview]
Message-ID: <388526407.00819@tsinghua.org.cn> (raw)
Hi, Friends,
I am debuging the u-boot on freescale MPC8360, the version of u-boot is 1.2.0, the
code on flash is OK,but the code from FLASH to DDR is broken, that is, after the
relocate_code function, the u-boot start again. I tested the DDR on u-boot, it's
OK. I was wondering that hot to deal with this problem? follow is the COM output
from u-boot. Thanks.
U-Boot 1.2.0 (Aug 29 2007 - 20:50:37) MPC83XX
Clock configuration:
Coherent System Bus: 264 MHz
Core: 528 MHz
QE: 198 MHz
Local Bus Controller: 264 MHz
Local Bus: 66 MHz
DDR: 264 MHz
DDR Secondary: 264 MHz
SEC: 88 MHz
I2C1: 264 MHz
I2C2: 264 MHz
CPU: Rev: Unknown guojing modified source code
Rev: 20 at 528 MHz
Board: Freescale MPC8360EMDS
I2C: ready
DRAM:
SDRAM on Local Bus: 64 MB
DDR RAM: 256 MB
DDR test phase 1:
DDR test phase 2:
DDR test passed.
init_sequence finished
begin set up a new stack
beginning memcpy
ended memcpy,beginning relocate_code
U-Boot 1.2.0 (Aug 29 2007 - 20:50:37) MPC83XX
Clock configuration:
Coherent System Bus: 264 MHz
Core: 528 MHz
QE: 198 MHz
Local Bus Controller: 264 MHz
Local Bus: 66 MHz
DDR: 264 MHz
DDR Secondary: 264 MHz
SEC: 88 MHz
I2C1: 264 MHz
I2C2: 264 MHz
CPU: Rev: Unknown guojing modified source code
Rev: 20 at 528 MHz
Board: Freescale MPC8360EMDS
I2C: ready
DRAM:
SDRAM on Local Bus: 64 MB
DDR RAM: 256 MB
DDR test phase 1:
DDR test phase 2:
DDR test passed.
init_sequence finished
begin set up a new stack
beginning memcpy
ended memcpy,beginning relocate_code
next reply other threads:[~2007-08-31 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 2:13 郭劲 [this message]
2007-09-02 2:01 ` Re:The question about the relocate_code on u-boot for MPC8360? jxnuxdy
2007-09-06 3:12 ` The " Paul Gortmaker
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=388526407.00819@tsinghua.org.cn \
--to=guojin02@tsinghua$(echo .)org.cn \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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