On 13-08-29 12:36 AM, Elvis Dowson wrote:
On Aug 29, 2013, at 2:43 AM, Bruce Ashfield <[email protected]>
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
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
