qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Xiao Jiang <jgq516@gmail.com>
To: David Gilbert <david.gilbert@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] How to run realview-pbx-a9 image in qemu
Date: Tue, 12 Jul 2011 14:04:09 +0800	[thread overview]
Message-ID: <4E1BE3D9.7010903@gmail.com> (raw)
In-Reply-To: <4E1BC953.5010904@gmail.com>

Xiao Jiang wrote:
> David Gilbert wrote:
>> On 11 July 2011 09:21, Xiao Jiang <jgq516@gmail.com> wrote:
>>  
>>> Hello,
>>>
>>> I downloaded latest qemu 0.14.1, it should support realview-pbx-a9 
>>> board now
>>> from
>>> below cmd.
>>> $ qemu-system-arm -M ?|grep Cortex-A9
>>> realview-pbx-a9 ARM RealView Platform Baseboard Explore for Cortex-A9
>>>
>>> Then I compiled a zImage from latest mainline with use
>>> realview-smp_defconfig as config
>>> file, but unfortunately qemu can't run with the image, I had tried 
>>> the below
>>> instructions.
>>> 1. qemu-system-arm -M realview-pbx-a9 -kernel zImage -initrd initrd.img
>>> -nographic -append "console=ttyAMA0"
>>> 2. qemu-system-arm -M realview-pbx-a9 -m 1024M -kernel zImage 
>>> -nographic
>>> -append "root=/dev/nfs nfsroot=128.225.160.22:/home/work/rootfs rw
>>> console=ttyAMA0 rdinit=/sbin/init" -net nic -net 
>>> tap,ifname=tap0,script=no
>>> Both instructions can't work, console is hang and no informations is
>>> appeared.
>>> so I am wondering if there are something wrong about the kernel, am 
>>> I choose
>>> the wrong
>>> config file for realview-pbx-a9 board? Or the native mainline kernel 
>>> can't
>>> boot on
>>> qemu? Any suggestions? Thanks a lot!
>>>     
>>
>> The command I use is:
>>
>> sudo ./arm-softmmu/qemu-system-arm -M realview-pbx-a9 -m 1024 -kernel
>> thekernel -serial telnet::4444,server -append "console=earlycon
>> console=ttyS0 console=ttyAMA0 earlyprintk root=/dev/nfs
>> nfsroot=10.1.1.1:/armroot rw
>> ip=10.1.1.2:10.1.1.1:10.1.1.1:255.255.255.0:armqemu nfsrootdebug "
>> -net nic -net tap,ifname=tap0,script=no,downscript=no
>>
>> and then telnet to port 4444 to get the console.
>>
>> (I'm using the linaro qemu tree).
>>
>>   
> Hi Dave,
>
> It looks like I am not in luck, qemu still can't run successfully.
> I recompiled the qemu from linaro qemu tree and executed below
> instructions in order.
>
> 1. open window A, run below cmd.
> xjiang@xjiang-desktop:~/work/qemu$ sudo qemu-system-arm -M 
> realview-pbx-a9 -m 1024 -kernel zImage-cortex-a9 -serial 
> telnet::4444,server -append "console=earlycon console=ttyS0 
> console=ttyAMA0 earlyprintk root=/dev/nfs 
> nfsroot=10.1.6.6:/home/gjiang/work/ti_sitara_am35xx-standard-glibc_std 
> ip=10.1.6.8:10.1.6.6:10.1.6.1:255.255.255.0" -net nic,vlan=0 -net 
> tap,vlan=0,ifname=tap0,script=no,downscript=no
> QEMU waiting for connection on: telnet:0.0.0.0:4444,server
>
> 2. open another window B, telnet to port 4444.
> xjiang@xjiang-desktop$ telnet localhost 4444
> Trying ::1...
> Trying 127.0.0.1...
> Connected to localhost.
> Escape character is '^]'.
> Connection closed by foreign host.
>
> 3, Then in window A, "VNC server running on `127.0.0.1:5901'" is 
> appeared,
> so I open terminal service client, set the computer name to 
> 127.0.0.1:5901
> and selected vnc protocol. But after I clicked connect I can't see any 
> infos,
> and the window named as "TightVNC: QEMU" is totally black.
>
Fatal infos appeared in window A after some time, pls see belows.
xjiang@xjiang-desktop:~/work/qemu$ sudo qemu-system-arm -M 
realview-pbx-a9 -m 1024 -kernel zImage-cortex-a9 -serial 
telnet::4444,server -append "console=earlycon console=ttyS0 
console=ttyAMA0 earlyprintk root=/dev/nfs 
nfsroot=10.1.6.6:/home/gjiang/work/ti_sitara_am35xx-standard-glibc_std 
ip=10.1.6.8:10.1.6.6:10.1.6.1:255.255.255.0" -net nic,vlan=0 -net 
tap,vlan=0,ifname=tap0,script=no,downscript=no
QEMU waiting for connection on: telnet:0.0.0.0:4444,server
VNC server running on `127.0.0.1:5901'
qemu: fatal: Trying to execute code outside RAM or ROM at 0x10000000

R00=c03442e4 R01=00000124 R02=00000000 R03=c02ced38
R04=00000000 R05=00208f4c R06=0020799c R07=00000001
R08=00000009 R09=00209a74 R10=27d312c8 R11=00208a20
R12=0001b80e R13=002088b0 R14=00101a08 R15=10000000
PSR=200001d3 --C- A svc32

Thanks,
Xiao
> Are there something wrong in above instructions? or there are other 
> necessary
> cmds which I have missed? Thanks in advance!
>
> Regards,
> Xiao 
>> Dave
>>   
>
>

  reply	other threads:[~2011-07-12  5:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-11  8:21 [Qemu-devel] How to run realview-pbx-a9 image in qemu Xiao Jiang
2011-07-11  8:52 ` David Gilbert
2011-07-11  9:32   ` Xiao Jiang
2011-07-12  4:10   ` Xiao Jiang
2011-07-12  6:04     ` Xiao Jiang [this message]
2011-07-12  9:00       ` David Gilbert
2011-07-12 10:00         ` Xiao Jiang
2011-09-27 13:01           ` loody
2011-09-27 13:18             ` David Gilbert
2011-09-27 13:48               ` loody
2011-09-28  0:59                 ` Xiao Jiang

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=4E1BE3D9.7010903@gmail.com \
    --to=jgq516@gmail.com \
    --cc=david.gilbert@linaro.org \
    --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).