From: "Comicinker" <comicinker@gmx.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] New machine?
Date: Fri, 28 Jan 2011 18:00:08 +0100 [thread overview]
Message-ID: <20110128170008.139840@gmx.net> (raw)
Hi,
I want to boot a embedded linux environment in qemu, namely xxsvideo [1]. It is for an arm based fujitsu development board [2]. The toolchain provideds finally 3 files to flash the target device:
-----
comicinker@hardy:~/workspace/jade_rootfs_build-0.8.5/images$ ls -lh
insgesamt 5,4M
-rw-r--r-- 1 comicinker comicinker 3,9M 2011-01-22 19:21 rootfs-xxsvideo-jadeevalkit-0.8.5.bin
-rwxr-xr-x 1 comicinker comicinker 110K 2011-01-22 19:17 u-boot-xxsvideo-jadeevalkit-0.8.5.bin
-rw-r--r-- 1 comicinker comicinker 1,4M 2011-01-22 19:21 uImage-xxsvideo-jadeevalkit-0.8.5.bin
-----
The documentation of xxsvideo tells the following about the Kernel:
-----
3.2 Kernel
Currently the following flash partition is used. This may change e.g. to reserve space for a
splash-image:
cat /proc/mtd
dev: size erasesize name
mtd0: 00020000 00020000 "u-boot"
mtd1: 00020000 00020000 "u-boot var"
mtd2: 00200000 00020000 "kernel"
mtd3: 01dc0000 00020000 "rootfs"
To install the kernel to flash, put the image (images/uImage-xxsvideo-jadeevalkit-0.8.4.bin)
to your tftpboot-directory and type on the u-boot console:
xxsvideo> set autostart no
xxsvideo> tftpboot 0x40500000 uImage-xxsvideo-jadeevalkit-0.8.4.bin
xxsvideo> erase 0x10040000 0x1023ffff
xxsvideo> cp.b 0x40500000 0x10040000 $(filesize)
To install the kernel inside the running linux, do:
flashcp --verbose /tmp/uImage /dev/mtd2
-----
I tried to boot the Kernel with the following command:
qemu-system-arm -kernel uImage-xxsvideo-jadeevalkit-0.8.5.bin -M integratorcp -nographic
And qemu returns with following error message:
-----
qemu: fatal: Trying to execute code outside RAM or ROM at 0x40008000
R00=00000000 R01=00000113 R02=00000100 R03=00000000
R04=00000000 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=00000000 R14=00000000 R15=40008000
PSR=400001d3 -Z-- A svc32
s00=00000000( 0) s01=00000000( 0) d00=0000000000000000( 0)
[...]
-----
How can I boot the kernel, or u-boot? Do I have to patch qemu to support a new machine? In my ideal imagination, I just tell qemu about the jffs2/mtd images/files and specify eventually some memory addresses. How could I do that?
Thanks in advance!
Comicinker
[1] http://sourceforge.net/projects/xxsvideo/
[2] http://www.fujitsu.com/emea/services/microelectronics/gdc/gdcdevices/mb86r01-jade.html
--
NEU: FreePhone - kostenlos mobil telefonieren und surfen!
Jetzt informieren: http://www.gmx.net/de/go/freephone
next reply other threads:[~2011-01-28 17:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 17:00 Comicinker [this message]
2011-01-30 11:13 ` [Qemu-devel] New machine? Peter Maydell
2011-02-04 0:31 ` comicinker
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=20110128170008.139840@gmx.net \
--to=comicinker@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.