From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mail.openembedded.org (Postfix) with ESMTP id 559E86BA1B for ; Thu, 29 Aug 2013 12:35:59 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r7TCZuY1012170 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 29 Aug 2013 05:35:56 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.2.347.0; Thu, 29 Aug 2013 05:35:56 -0700 Message-ID: <521F4020.1080800@windriver.com> Date: Thu, 29 Aug 2013 08:35:44 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 To: Elvis Dowson References: <20130825104341.a5c5c4a29245e5c988b774ab8f895ac5.305c945aa2.wbe@email15.secureserver.net> <835D4942-DCEA-4634-9822-24ADDCAD8DF7@gmail.com> <092BF80A-B02A-4506-840E-2EEEE48CE298@gmail.com> <4AC41A5E-073D-4973-82BD-F94A8B168F34@gmail.com> <521AA95A.8000803@windriver.com> <7DBFB4EE-4727-422F-8815-D801827A37C9@gmail.com> <521AD896.3000503@windriver.com> <6324D287-2CA2-4A88-AFF4-58CABE82B2CC@gmail.com> <521BA7CB.7070206@windriver.com> <2D33FB6A-9F7F-4E8E-8B1A-CED1D571A82C@gmail.com> <521D0622.6090802@windriver.com> <2AC87191-8D2B-4972-A249-2043B68A0A7B@gmail.com> <521E7D2E.6060404@windriver.com> In-Reply-To: Cc: OpenEmbedded Core Mailing List Subject: Re: QEMU with ARM Cortex A9 with hard float configuration - Kernel panic X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Aug 2013 12:36:00 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 13-08-29 12:36 AM, Elvis Dowson wrote: > > On Aug 29, 2013, at 2:43 AM, Bruce Ashfield wrote: > >> On 13-08-28 11:16 AM, Elvis Dowson wrote: >>> Hi, >>> I get the following error while running the bitbake linux-yocto >>> command for a qemu machine conf that I'm building. The build system is >>> unable to find the dtc binary: >>> >>> | make: Leaving directory >>> `/tool/yocto/poky/build/tmp/work/qemuarma9-poky-linux-gnueabi/linux-yocto/3.4.52+gitAUTOINC+7250de4d4a_4122d6cf3f-r4.5/image/usr/src/kernel' >>> | NOTE: make -j 6 vexpress-v2p-ca9.dtb >>> | DTC arch/arm/boot/vexpress-v2p-ca9.dtb >>> | /bin/sh: >>> /tool/yocto/poky/build/tmp/work/qemuarma9-poky-linux-gnueabi/linux-yocto/3.4.52+gitAUTOINC+7250de4d4a_4122d6cf3f-r4.5/linux-qemuarma9-standard-build/scripts/dtc/dtc: >>> No such file or directory >>> | make[3]: *** [arch/arm/boot/vexpress-v2p-ca9.dtb] Error 1 >>> | make[2]: *** [vexpress-v2p-ca9.dtb] Error 2 >>> | make[1]: *** [sub-make] Error 2 >>> | make: *** [all] Error 2 >>> | ERROR: oe_runmake failed >>> | WARNING: >>> /tool/yocto/poky/build/tmp/work/qemuarma9-poky-linux-gnueabi/linux-yocto/3.4.52+gitAUTOINC+7250de4d4a_4122d6cf3f-r4.5/temp/run.do_install.10606:1 >>> exit 1 from >>> | exit 1 >>> | ERROR: Function failed: do_install (log file is located at >>> /tool/yocto/poky/build/tmp/work/qemuarma9-poky-linux-gnueabi/linux-yocto/3.4.52+gitAUTOINC+7250de4d4a_4122d6cf3f-r4.5/temp/log.do_install.10606) >>> ERROR: Task 4 >>> (/tool/yocto/poky/meta/recipes-kernel/linux/linux-yocto_3.4.bb, >>> do_install) failed with exit code '1' >>> NOTE: Tasks Summary: Attempted 598 tasks of which 597 didn't need to be >>> rerun and 1 failed. >> >> Did you ever get past this ? It looks like the recent device tree >> changes where we use the kernel dtc versus an external dtc are causing >> you a problem. > > I did get past this, after I updated the SRCREV_meta with the correct commit, > which resulted in the correct kconfig fragment being picked up, with enabled > the device tree option in the kernel. > > However, I'm unable to get qemu to boot correctly, for both ARM Cortex A9 > and ARM Cortex A* (beagle). Maybe this has to do with the fact that it needs > xload+uboot in addition to the kernel, using an SD card image. > > Any suggestions on how I can do this? > With that, it's always been a manual setup for me in the past. The typical workflow is to test them via the usermode NFS boot. Have you given that a go ? Once I'm over the 3.10 introduction curve, I'm happy to dust off my old A9 support and get the right qemu support for a full system boot. Cheers, Bruce > I'd like to know how qemuarmv6, qemuarmv9 and qemuarma9 were tested > earlier. > > I think its important to get atleast the A8 and A( QEMU platforms up and running > in oe-core, since they represent a bunch of the current targets used for actual > development. > > Best regards, > > Elvis Dowson >