On 16 February 2017 at 18:40, Pello Heriz <pello.he...@alumni.mondragon.edu> wrote: > Hello, > > I have executed bitbake for ZCU102 machine and now I'm trying to launch it > on Xilinx's QEMU using runqemu zcu102-zynqmp command. However, I'm not > getting the expected result, just because the kernel never starts, so what I > have is a ZynqMP u-boot terminal. > > Here it is the summary of the QEMU launch: > > ------------------------------------------------------------------------------------------------------------- > pello@pello-VirtualBox:/opt/yocto_GE/yocto_master/poky/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_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp > runqemu - INFO - Running ls -t > /opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/*.qemuboot.conf... > runqemu - INFO - CONFFILE: > /opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170214102917.qemuboot.conf > runqemu - INFO - Continuing with the following parameters: > > KERNEL: > [/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/Image] > DTB: > [/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/Image-zynqmp-zcu102-revB.dtb] > MACHINE: [zcu102-zynqmp] > FSTYPE: [cpio.gz.u-boot] > ROOTFS: > [/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170214102917.rootfs.cpio.gz.u-boot] > CONFFILE: > [/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170214102917.qemuboot.conf] > > runqemu - INFO - Running /sbin/ip link... > runqemu - INFO - Setting up tap interface under sudo > runqemu - INFO - Acquiring lockfile /tmp/qemu-tap-locks/tap0.lock... > runqemu - INFO - Created tap: tap0 > runqemu - INFO - Running ldd > /opt/yocto_GE/yocto_master/poky/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/qemu-xilinx/qemu-system-aarch64... > runqemu - INFO - Running > /opt/yocto_GE/yocto_master/poky/build/tmp/work/zcu102_zynqmp-poky-linux/core-image-minimal/1.0-r0/recipe-sysroot-native/usr/bin/qemu-xilinx/qemu-system-aarch64 > -net nic -net nic -net nic -net nic,netdev=net0,macaddr=52:54:00:12:34:02 > -netdev tap,id=net0,ifname=tap0,script=no,downscript=no -device > loader,addr=0x6000000,file=/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/core-image-minimal-zcu102-zynqmp-20170214102917.rootfs.cpio.gz.u-boot,force-raw=true > -nographic -serial mon:stdio -serial null -hw-dtb > /opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/qemu-hw-devicetrees/zcu102-arm.dtb > -device loader,addr=0xfd1a0104,data=0x8000000e,data-len=4 -device > loader,file=/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/arm-trusted-firmware-zcu102-zynqmp.elf,cpu-num=0 > -device > loader,file=/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/u-boot.elf > -device > loader,addr=0x4000000,file=/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/Image-zynqmp-zcu102-revB.dtb > -device > loader,addr=0x80000,file=/opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/Image > -machine arm-generic-fdt -m 2048 -kernel > /opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/Image > -append 'root=/dev/vda rw highres=off mem=2048M > ip=192.168.7.2::192.168.7.1:255.255.255.0 ' -dtb > /opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/Image-zynqmp-zcu102-revB.dtb > Warning: vlan 0 is not connected to host network > rom: requested regions overlap (rom phdr #0: > /opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/arm-trusted-firmware-zcu102-zynqmp.elf. > free=0x00000000ffff9000, addr=0x00000000fffe0000) > rom: requested regions overlap (rom > /opt/yocto_GE/yocto_master/poky/build/tmp/deploy/images/zcu102-zynqmp/Image. > free=0x00000000fffffff8, addr=0x0000000000080000) > NOTICE: ATF running on XCZUUNKN/QEMU v1/RTL0.0 at 0xfffea000 > NOTICE: BL31: Secure code at 0x60000000 > NOTICE: BL31: Non secure code at 0x8000000 > NOTICE: BL31: v1.2(release):a9e3716 > NOTICE: BL31: Built : 14:02:12, Feb 14 2017 > > > U-Boot 2016.07 (Feb 14 2017 - 15:02:22 +0100) Xilinx ZynqMP ZCU102 revB > > I2C: ready > DRAM: 4 GiB > EL Level: EL2 > Chip ID: xczuunknown > MMC: sdhci@ff170000: 0 > Using default environment > > In: serial@ff000000 > Out: serial@ff000000 > Err: serial@ff000000 > Bootmode: JTAG_MODE > SCSI: SATA link 0 timeout. > SATA link 1 timeout. > AHCI 0001.0000 32 slots 2 ports 1.5 Gbps 0x3 impl SATA mode > flags: ncq only > scanning bus for devices... > Found 0 device(s). > Net: ZYNQ GEM: ff0e0000, phyaddr 12, interface rgmii-id > eth0: ethernet@ff0e0000 > Error: ethernet@ff0e0000 address ff:ff:ff:ff:ff:ff illegal value > > Hit any key to stop autoboot: 0 > *** ERROR: `serverip' not set > ZynqMP> > > ------------------------------------------------------------------------------------------------------------- > > Does anybody knows what's happening? Why I'm getting the serverip error too?
The severip error is because it is attempting to run a tftpboot command within the default bootcmd. But if you grab the current master of meta-xilinx I have just merged the patch series I sent out last week which included a change for JTAG auto-boot for zynqmp for this exact purpose :). http://git.yoctoproject.org/cgit/cgit.cgi/meta-xilinx/commit/?id=064b144ca332942487a9ab6de0a892987b4307ef Regards, Nathan > > I would be very pleased with any answer, > Thanks, > Pello > > -- > _______________________________________________ > meta-xilinx mailing list > meta-xilinx@yoctoproject.org > https://lists.yoctoproject.org/listinfo/meta-xilinx > -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
