From: 郭劲 <guojin02@tsinghua.org.cn>
To: linuxppc-embedded@ozlabs.org
Subject: The question about the fail at the begin of linux on MPC8360E.
Date: Fri, 02 Nov 2007 11:08:37 +0800 [thread overview]
Message-ID: <393972917.10298@tsinghua.org.cn> (raw)
Hi,friends,
Thanks.
We boot the linux-2.6.22 on MPC8360 board, it failed, follow is the output
information. we just only success on linux-2.6.11, but fail on linux-2.6.19 and
linux-2.6.22. Both 2.6.19 and 2.6.22 are failed on same position,please see follow
information. linux-2.6.19 and linux-2.6.22 are come from BSP of freescale. I used
the u-boot-1.2.0 that compiled by myself. We guess that maybe we did not setup the
bootargs parameter on u-boot rightly or maybe the DDR-I hardware circuit design is
not good enough.
If the reason is the bootargs parameter, could you tell me what is the right
bootargs for linux-2.6.19 and linux-2.6.22?
If the reason is the DDR, I want to boot the linux on my SDRAM chip,kick off the
DDR, my SDRAM located on the address of F0000000~F3FFFFFF, total 64MB. How can I
modify the source code of linux to re-map it and ramdisk and others to my SDRAM
chip space?
Follow is the fail information:
=> bootm 0c000000 0e000000
## Booting image at 0c000000 ...
Image Name: Linux-2.6.22
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 1333681 Bytes = 1.3 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 0e000000 ...
Image Name: uboot ext2 ramdisk rootfs
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 3589813 Bytes = 3.4 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Ramdisk to 0fc3e000, end 0ffaa6b5 ... OK
next reply other threads:[~2007-11-02 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-02 3:08 郭劲 [this message]
2007-11-02 12:55 ` The question about the fail at the begin of linux on MPC8360E Medve Emilian-EMMEDVE1
2007-11-02 13:54 ` Timur Tabi
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=393972917.10298@tsinghua.org.cn \
--to=guojin02@tsinghua.org.cn \
--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;
as well as URLs for NNTP newsgroup(s).