From: daixiaoke <daixiaoke@cn.fujitsu.com>
To: qemu-devel@nongnu.org
Cc: fnst-ulinux <fnst-ulinux@cn.fujitsu.com>
Subject: [Qemu-devel] The process of kernel cross-compiling in arm-test-0.2.tar.gz
Date: Mon, 23 May 2011 17:26:45 +0800 [thread overview]
Message-ID: <4DDA2855.6000003@cn.fujitsu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
Hi,
I am trying to run uClinux by qemu. The problem is:
The files generated after cross-compiling uClinux can't be used by qemu to
run uClinux successfully.
However, qemu can successfully run the system via the files in arm-test-0.2.tar.gz,
which can be downloaded from sector "QEMU disk images" on http://wiki.qemu.org/Download.
My process:
1.Installing qemu-0.14.1 and Sourcery G++ in my virtual system(RHEL6.0).
2.Downloading uClinux-dist-20080808-20090112.patch.gz & uClinux-dist-20080808.tar.bz2
3.Compiled uClinux following steps in the attachment(Chapter 4: Building the uClinux image).
“STM3210E-EVAL-jffs” was selected for "Porduct" while Configure uClinux for STM3210E-EVAL.
4.After compiled, 3 files generated: xipImage.bin, rootfs.img.bin and logo.bin
5.Executed following command on command line:
qemu-system-arm -kernel xipImage.bin -initrd rootfs.img.bin -nographic -append "console=ttyAMA0"
But it didn't work and nothing was shown out on the command line.
So could Paul Brook or someone else tell me the process of kernel cross-compiling in
arm-test-0.2.tar.gz?
Or, how should I compile uClinux to make the files created usefully for qemu?
Thanks,
Dai Xiaoke
[-- Attachment #2: CD00242717.pdf --]
[-- Type: application/pdf, Size: 890333 bytes --]
next reply other threads:[~2011-05-23 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-23 9:26 daixiaoke [this message]
2011-05-23 11:19 ` [Qemu-devel] The process of kernel cross-compiling in arm-test-0.2.tar.gz Brad Hards
2011-05-24 1:44 ` daixiaoke
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=4DDA2855.6000003@cn.fujitsu.com \
--to=daixiaoke@cn.fujitsu.com \
--cc=fnst-ulinux@cn.fujitsu.com \
--cc=qemu-devel@nongnu.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).