On Tue, Feb 7, 2017 at 2:31 AM, Pello Heriz <[email protected]> wrote: > Hi, > > I'm trying to test my ZCU102 minimal image on QEMU emulator (I'm using Morty > branch). > > I have got to compile the image, but when I execute 'runqemu zcu102-zynqmp' > command, everything looks to go OK until the execution arrives to this point > and get stack. > > pello@pello-VirtualBox:/opt/yocto/poky/2.2/new_zcu102/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: > /opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp > runqemu - INFO - Running ls -t > /opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/*.qemuboot.conf... > runqemu - INFO - CONFFILE: > /opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170203125134.qemuboot.conf > runqemu - INFO - Continuing with the following parameters: > > KERNEL: > [/opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/Image] > DTB: > [/opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/Image-zynqmp-zcu102-revB.dtb] > MACHINE: [zcu102-zynqmp] > FSTYPE: [cpio] > ROOTFS: > [/opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170203125134.rootfs.cpio] > CONFFILE: > [/opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170203125134.qemuboot.conf] > > runqemu - INFO - Running /sbin/ip link... > runqemu - INFO - Setting up tap interface under sudo > [sudo] password for pello: > Lo sentimos, vuelva a intentarlo. > [sudo] password for pello: > runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock... > runqemu - INFO - Created tap: tap0 > runqemu - INFO - Running ldd > /opt/yocto/poky/2.2/new_zcu102/build/tmp/sysroots/x86_64-linux/usr/bin/qemu-system-aarch64... > runqemu - INFO - Running > /opt/yocto/poky/2.2/new_zcu102/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 > /opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170203125134.rootfs.cpio > -nographic -serial mon:stdio -serial null -kernel > /opt/yocto/poky/2.2/new_zcu102/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 > /opt/yocto/poky/2.2/new_zcu102/build/tmp/deploy/images/zcu102-zynqmp/Image-zynqmp-zcu102-revB.dtb > Warning: vlan 0 is not connected to host network > > As you can see, the program get stack in this line and I don´t know why.
Hello Pello, Nothing is stuck QEMU is running and trying to boot your images. Unfortunately we don't have all of the support in mainline QEMU to boot the Xilinx kernel for the ZCU102 and the kernel is panicking. You will need to use the Xilinx fork of QEMU. You can do this by setting 'XILINX_QEMU = "1'"' in your locall.conf (you will need to delete your tmp and rebuild after that). Then you should be able to boot your images on QEMU. Thanks, Alistair > > I would be very pleased if you answer to me as soon as possible. > Looking forward to your answer, > Best regards, > Pello > > -- > _______________________________________________ > meta-xilinx mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-xilinx > -- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
