[meta-xilinx] QEMU produced no output
Alistair Francis
alistair23 at gmail.com
Mon Jan 16 14:38:01 PST 2017
On Sun, Jan 15, 2017 at 9:34 AM, Alistair Francis <alistair23 at gmail.com> wrote:
> On Sun, Jan 15, 2017 at 3:44 AM, Peter Smith <salerio at gmail.com> wrote:
>> Hi,
>>
>> I have built core-image-minimal from Morty branches of poky and meta-xilinx,
>> build completes withoiut issue (providing I remove ATF from image extra
>> dependsdue to the binutils issue). I then do a runqemu zcu102-zynqmp whuich
>> produces the following output and no more. I can get back to the QEMU
>> console no qemu is still running OK. I have read in other places that this
>> problem has been seen before when booting without u-boot, is this the same
>> or a new problem?
>
> Hey Peter,
>
> I have noticed that issue as well. I'm not sure why the guest isn't
> running or printing output. I'll look into it and send some patches to
> hopefully fix it.
>
> If you want you can try my latest patch set and see if that works.
Unfortunately QEMU 2.7.0 doesn't support running the full ZCU102
image. This is the kernel panic that is occurring:
[ 12711.536] Mountpoint-cache hash table entries: 4096 (order:
3, 32768 bytes)
[ 29569.056] ASID allocator initialised with 65536 entries
[ 86775.984] swapper/0[1]: undefined instruction: pc=ffffff800847218c
[ 87069.104] Code: d65f03c0 12800240 d65f03c0 aa0303f2 (d4000003)
[ 87517.216] Internal error: Oops - undefined instruction: 0
[#1] PREEMPT SMP
[ 87785.536] Modules linked in:
[ 88199.280] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
4.6.0-xilinx-v2016.3 #1
[ 88338.960] Hardware name: ZynqMP ZCU102 RevB (DT)
[ 88519.648] task: ffffffc071866b80 ti: ffffffc071868000
task.ti: ffffffc071868000
[ 88723.792] PC is at do_fw_call_smc+0x4/0x58
[ 88848.944] LR is at zynqmp_pm_get_api_version.part.0+0x30/0x80
[ 88971.168] pc : [<ffffff800847218c>] lr : [<ffffff8008472740>]
pstate: 00000245
[ 89111.824] sp : ffffffc07186bd50
[ 89214.704] x29: ffffffc07186bd50 x28: 0000000000000000
[ 89392.864] x27: 0000000000000000 x26: 0000000000000000
[ 89528.080] x25: 0000000000000000 x24: 0000000000000000
[ 89658.480] x23: 0000000000000000 x22: ffffffbffe800cac
[ 89788.928] x21: ffffff8008c3f000 x20: ffffff8008ce2000
[ 89919.472] x19: ffffff8008ce26f8 x18: ffffffc07186bd78
[ 90063.904] x17: 0000000000000001 x16: 00000000124ffbbc
[ 90194.784] x15: ffffffffffffffff x14: ffffffffffffffff
[ 90324.960] x13: 0000000000000038 x12: 0101010101010101
[ 90454.944] x11: 0000000000000004 x10: 0101010101010101
[ 90633.600] x9 : 0000000000000004 x8 : 0000000000000004
[ 90769.296] x7 : 0000000000000008 x6 : 0000000000000000
[ 90902.832] x5 : 00636d73ffffffff x4 : ffffff8008472188
[ 91031.968] x3 : ffffffc07186bd78 x2 : 0000000000000000
[ 91160.752] x1 : 0000000000000000 x0 : 00000000c2000001
I don't have an easy way to fix this, it just isn't supported in
mainline QEMU 2.7.0 or 2.8.0 (which is the latest release).
We will have to wait until mainline QEMU support improves which Xilinx
and others are working on. In the meantime you can use Xilinx's fork
of QEMU. I am posting a newer patchset to support this and hopefully
it will be merged soon.
Thanks,
Alistair
>
> Thanks,
>
> Alistair
>
>>
>>
>> peter at peter-VirtualBox:/media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build$
>> runqemu zcu102-zynqmp
>> runqemu - INFO - Assuming MACHINE = zcu102-zynqmp
>> runqemu - INFO - Running MACHINE=zcu102-zynqmp bitbake -e...
>> runqemu - INFO - MACHINE: zcu102-zynqmp
>> runqemu - INFO - DEPLOY_DIR_IMAGE:
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp
>> runqemu - INFO - Running ls -t
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/*.qemuboot.conf...
>> runqemu - INFO - CONFFILE:
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170114175046.qemuboot.conf
>> runqemu - INFO - Continuing with the following parameters:
>>
>> KERNEL:
>> [/media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/Image]
>> DTB:
>> [/media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/Image-zynqmp-zcu102-revB.dtb]
>> MACHINE: [zcu102-zynqmp]
>> FSTYPE: [cpio]
>> ROOTFS:
>> [/media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170114201401.rootfs.cpio]
>> CONFFILE:
>> [/media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170114175046.qemuboot.conf]
>>
>> runqemu - INFO - Running /sbin/ip link...
>> runqemu - INFO - Setting up tap interface under sudo
>> [sudo] password for peter:
>> runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock...
>> runqemu - INFO - Created tap: tap0
>> runqemu - INFO - Running ldd
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-aarch64...
>> runqemu - INFO - Running
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-aarch64
>> -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -net nic -net nic
>> -net nic -net nic,netdev=net0,macaddr=52:54:00:12:34:02 -machine
>> xlnx-zcu102 -m 2048 -initrd
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170114201401.rootfs.cpio
>> -nographic -serial mon:stdio -serial null -kernel
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/Image
>> -append 'root=/dev/ram0 rw debugshell mem=2048M
>> ip=192.168.7.2::192.168.7.1:255.255.255.0 console=ttyPS0,115200 earlyprintk'
>> -dtb
>> /media/peter/47b5785c-f3af-4568-b073-30b79b3bd537/peter/Morty/build/tmp/deploy/images/zcu102-zynqmp/Image-zynqmp-zcu102-revB.dtb
>> Warning: vlan 0 is not connected to host network
>>
>>
>>
>> --
>> Best Regards
>> Peter
>>
>> --
>> _______________________________________________
>> meta-xilinx mailing list
>> meta-xilinx at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-xilinx
>>
More information about the meta-xilinx
mailing list